Professional Documents
Culture Documents
HitachiTuningManager TroubleshootingGuide
HitachiTuningManager TroubleshootingGuide
HitachiTuningManager TroubleshootingGuide
Hitachi, Ltd.
All Rights Reserved. CopyrightHitachi, Ltd. You cannot use this document except for the purpose of
doing troubleshoot of Hitachi Tuning Manager. And note that behaviors such as reproducing or revising or
opening in the public for this document are strictly prohibited by Hitachi, Ltd.
-PrefaceThis document is made for local engineers or support engineers of Hitachi Tuning Manager who
engages to do troubleshoot of the products. It is expected that local engineers or support engineers
can check the trouble and chase the cause by using this document. And we expect that this document
will help local engineers and support engineers with doing troubleshoot and they can manage to
solve the cause or indicating proper instruction for our customers.
This document provides information related to Hitachi Tuning Manager versions 6 and later. For
details about earlier versions, see the documents for versions earlier than version 8.
Precautions
(1) When using version 8 of Hitachi Command Suite products, including Hitachi Tuning
Manager, knowledge of the following is required.
The following specifications from version 7 have been changed in version 8:
- The installation destination of the Tuning Manager server
- The installation destination of the common components
- The names of commands (hcmdsXXX) provided by the common components, and the
storage directories of the common components
- Port numbers
For details about the specification changes listed above, see the explanation in the following
manual:
Hitachi Command Suite Tuning Manager Installation Guide
3 Installing or upgrading the Tuning Manager server
Concerning upgrade installations
Items to be checked after upgrading Tuning Manager
As a result of these changes, when you use the product and troubleshoot failures, you need to
observe the following items:
(a) Collecting RAS information
To collect the RAS information for version 8 or later of Tuning Manager server, use the
hcmds64getlogs command. You can also use this command to collect the RAS information
for 32-bit products (HFSM and HSNM2).
manual, substitute the terms used in this document with those used in the manual.
Hitachi Command Suite Tuning Manager Installation Guide
3 Installing or upgrading the Tuning Manager server
Concerning upgrade installations
Items to be checked after upgrading Tuning Manager
(2) When reading HPE OEM version, see this guide Appendix 6 For the HPE OEM version,
substitute the following terms as indicated.
- Revision history No
1
Contents revised
Date of revision
th
6 /March/2006
th
29 /March/2007
4th/June/2007
Revised by
Fukuda
Muraoka
Fukuda
st
Fukuda
th
31 /August/2007
14 /September/2007
Fukuda
27th/December/2007
Fukuda
th
30 /June/2008
Nishimoto
15th/July/2008
Nishimoto
th
6 /August/2008
st
Nishimoto
10
31 /October/2008
Nishimoto
11
28th/November/2008
Nishimoto
12
th
Nishimoto
th
28 /May/2009
13
30 /November/2009
Fukuda
14
28th/December/2009
Hisatomi
th
15
5 /March/2010
Tanaka
16
28th/April/2010
Tanaka
17
th
Tanaka
th
30 /June/2010
18
17 / September /2010
Tanaka
19
Tanaka
20
th
Fujimaki
st
15 /April/2011
21
31 /July/2011
Fujimaki
22
31st/October/2011
Y.Yamada
st
23
21 /February/2012
Y.Yamada
24
31st/May/2012
Y.Yamada
25
st
F.Kobayashi
st
31 /July/2012
26
31 /October/2012
F.Kobayashi
27
4th/February/2013
Y.Yamada
28
29
th
F.Kobayashi
th
F.Kobayashi
29 /April/2013
30 /September/2013
Hitachi Proprietary Information
30
31
30th/December/2013
F.Kobayashi
st
F.Kobayashi
th
31 /March/2014
32
25 /April/2014
F.Kobayashi
33
28th/July/2014
Y.Yamada
th
34
6 /October/2014
F.Kobayashi
35
1st/December/2014
F.Kobayashi
36
st
Y.Yamada
st
2 /February/2015
37
2 /March/2015
Y.Yamada
38
9th/April/2015
F.Kobayashi
39
th
F.Kobayashi
th
27 /April/2015
40
29 /June/2015
F.Kobayashi
41
3rd/August/2015
F.Kobayashi
nd
42
2 /November/2015
F.Kobayashi
43
16th/November/2015
F.Kobayashi
44
th
1 /February/2016
F.Kobayashi
-Abbreviations of Hitachi productsThis manual uses the following abbreviations for Hitachi product names.
Abbreviation
Agent
Collection Manager
DB2 Agent
In Ver.6 to 7.4
Hitachi Tuning Manager Agent for IBM DB2 Universal Database
In Ver.7.4.1 or later
Hitachi Tuning Manager - Agent for IBM DB2
Exchange Agent
Main Console
NAS Agent
Oracle Agent
Platform Agent(Unix)
Platform Agent(Windows)
Performance Reporter
or PR
RAID Agent
SQL Agent
Switch Agent
EAP Agent
HealthCheck Agent
OCI
ADO
Application Service
or HTnM REST Application
Service
HTnMAgent REST
Application Service
HTnM-Agent REST
Web Service
HTnM-Agent REST Services
-Abbreviation of other products or termsThis manual uses the following abbreviations for other product names or terms.
Abbreviation
API
CLI
CLPR
CRC
DAMP2
DHCP
DLL
DNS
EFCM
FQDN
GBIC
HA
High Availability
HBA
HDT
HDU
HTnM
HTM
HTML
I/O
Input/Output
IP
Internet Protocol
Ipv4
Ipv6
GUI
GUID
JRE
LAN
LDEV
Logical Device
LUSE
LUN
MIB
NAS
NIC
OS
Operating System
RAID
RFC
SAN
SCM
SNMP
SLPR
SSL
SSO
Single Sign On
SVP
Service Processor
SP
Service Pack
TBD
To Be Determined
TCP
TIA
UDP
VLAN
VxVM
WWN
WWW
XML
NTFS
NT File System
-Explanation of Terms for Version 8 or LaterThis manual for version 8 or later uses the following terms:
Term
Meaning
HBase
HBase32
HBase64
Description
Examples (*1)
<HBase-Installation-dir
For Windows:
ectory>
or
or
/opt/HiCommand/Base64
<HBase32-Installation-
For Windows:
directory>
Component
/opt/HiCommand/Base
<HBase64-Installation-
For Windows:
directory>
C:\Program Files\HiCommand\Base64
Component
/opt/HiCommand/Base64
<HTnM-Installation-dir
For Windows:
ectory>
For Unix:
/opt/HiCommand/TuningManager
(*1) This table lists the default installation directories. The examples of Windows installation
directories are for a 64-bit OS version where C: is specified for the system drive.
- Table of Corresponding Terms for Version 8 or LaterThe following table lists the terms used in this manual and their corresponding terms as used in
version 8 or later.
Term used in this manual
hcmdsdb
hcmds64db
hcmdsdbclustersetup
hcmds64dbclustersetup
hcmdsdbsrv
hcmds64dbsrv
hcmdsbackups
hcmds64backups
hcmdscancel
hcmds64cancel
hcmdsgetlogs
hcmds64getlogs
hcmdsintg
hcmds64intg
hcmdssrv
hcmds64srv
hcmdsweb2
hcmdsweb
HiCommand_log.jar
HiCommand_log_64.jar
HiCommand_log.hdb.jar
HiCommand_log_64.hdb.jar
HiCommand_log.db.jar
HiCommand_log_64.db.jar
HiCommand_log.csv.jar
HiCommand_log_64.csv.jar
9
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432N
ode
HKEY_LOCAL_MACHINE\SOFTWARE
HiRDBClusterService_HD0
HiRDBEmbeddedEdition_HD0
HiRDBClusterService_HD1
HiRDBEmbeddedEdition_HD1
10
Contents
1.
2.
2.1
2.2.
2.3.
2.4.
2.3.2.
2.3.3.
2.3.4.
Error during startup of Tuning Manager REST service (Ver. 8 or later) .................. 59
2.4.2.
2.4.3.
2.4.4.
2.4.5.
2.5.
2.6.
3.
4.
4.1.
4.2.
4.1.2.
4.1.3.
4.1.4.
4.1.5.
4.3.
The required time for executing the RAS command ..................................................... 104
4.6.
4.5.2
4.5.3
Prerequisites ....................................................................................................110
4.5.4
Collecting data when a problem occurs while displaying a chart in Adobe Flash
5.1
5.2
6.
5.2.1
5.2.1
Sequence for starting up the service of Tuning Manager server ........................... 129
6.1.
6.2.
6.3.
6.4.
7.
7.1.
7.2.
Caution when using Hitachi Tuning Manager with IE 6.0, IE 7.0 or IE 8.0
7.4.
7.5.
Caution for the case that HTnM is connected to HDvM 6.0.0 to 6.1.1 and is
Using the jpcctrl delete command with the force option (this option is in
7.8 How to confirm whether other programs are connected to HiRDB ...................................... 168
7.8.1 How to confirm whether other programs are connected to HiRDB by using Command 168
7.8.2 How to confirm whether other programs are connected to HiRDB from log file ......... 180
7.9 Adding an OUI Code (Switch Agent version 7.1 or later) ..................................................... 184
7.10 Overview of Agent Common Component ............................................................................. 188
7.11 About Agent for RAID Extention component ...................................................................... 189
7.12 Analytics tab ........................................................................................................................ 190
7.12.1 Internal architecture ............................................................................................. 190
7.12.2 Related properties files and log files ...................................................................... 190
7.12.3 Troubleshooting ................................................................................................... 192
7.12.4 How to examine the related logs (for versions 8 and later) ...................................... 199
7.13 Notes on removal ................................................................................................................. 200
7.13.1 Processes might remain after removal.................................................................... 200
7.14 Notes on using NAS Agent to monitor HNAS ..................................................................... 200
7.15 Performance data collection by using a TCP/IP connections for Agent for RAID............... 201
7.15.1 If the microcode version of the monitored storage system is not supported ............... 201
7.15.2 How acquisition of performance data is affected by a limit on the number of sessions 201
7.15.3 Typical causes of failure in performance data collection using TCP/IP connections ... 202
7.15.3.1 The microcode version of a storage system is not supported ................................. 202
7.15.3.2 Other processes are logged in to a storage system with the same user ID ............... 203
7.15.3.3 Other processes are collecting performance data from a storage system ................. 203
7.15.3.4 Memory is insufficient....................................................................................... 204
Appendix 1 List of metric ............................................................................................................................... 205
Appendix 2 Resource estimate tool................................................................................................................ 205
Appendix 3 Tuning Manager Deletion Procedures ...................................................................................... 206
3-a
Uninstall of the Tuning Manager server for Windows(Ver.5.1 to Ver.5.9) .................... 206
3-b
Deleting Tuning Manager server for Windows (In Ver.6.0.0 to earlier than
8.0.0)
206
3-c
3-b.1
3-b.2
3-b.3
3-b.4
3-b.5
Uninstall of the Tuning Manager server for Solaris(Ver.5.1 to Ver.5.9) ....................... 239
3-d Deleting Tuning Manager server for Solaris (In Ver.6.0.0 to earlier than 8.0.0) ................. 239
3-d.1
3-d.2
3-d.3
3-d.4
3-d.5
3-e Force uninstall of the Tuning Manager agents for Windows (In Ver.6.0.0 to earlier
than 8.0.0).................................................................................................................................... 250
3-e.1
3-e.2
3-e.3
3-e.4
The flow of the force deletion and re-install the agent ........................................ 251
3-e.5
3-e.6
3-f Force uninstall of the Tuning Manager agents for UNIX (In Ver.6.0.0 to earlier than
8.0.0)
261
3-f.1
3-f.2
3-f.3
3-f.4
The flow of the force deletion and re-install the agent ........................................ 262
3-f.5
3-f.6
3-g
Deleting Tuning Manager server for Linux (In Ver.7.1.0 to earlier than 8.0.0) ........... 265
3-g.1
3-g.2
3-g.3
3-g.4
3-g.5
3-h
Deleting Tuning Manager server for Windows (Ver.8 or later) ..................................... 276
3-h.1
3-h.2
3-h.3
3-h.4
3-h.5
3-i Deleting Tuning Manager server for Linux (Ver.8 or later)................................................... 314
3-i.1
3-i.2
3-i.3
3-i.4
3-i.5
3-j Force uninstall of the Tuning Manager agents for Windows (Ver.8 or later) ........................ 333
3-j.1
3-j.2
3-j.3
3-j.4
The flow of the force deletion and re-install the agent ........................................ 334
14
3-j.5
3-j.6
3-k Force uninstall of the Tuning Manager agents for UNIX (Ver.8 or later) ............................ 344
3-k.1
3-k.2
3-k.3
3-k.4
The flow of the force deletion and re-install the agent ........................................ 345
3-k.5
3-k.6
4-c.2
4-c.3
How to extend the size of the database log are ................................................... 354
4-c.4
Back to the size of the database area to the original ............................................ 362
7-a.2
7-a.3
7-a.4
7-a.5
Back up data for Hitachi Storage Command Suite products ................................ 386
7-a.6
Back up the definition information files for the Tuning Manager server ............... 387
7-a.7
Back up the definition information files for Performance Reporter ...................... 389
7-a.7(ii)
Back up the definition information files for Tuning Manager REST Application
7-a.9
7-a.10
Back up the definition information files for HTnM-Agent REST Services (Ver. 8 or
later)
392
7-a.11 Back up the performance data for Tuning Manager API (Ver. 8 or later) ................... 393
7-a.12 Back up the Hybrid Store (Ver. 8.1.3 or later) ......................................................... 393
7-b. Restore procedure on a host on which the Tuning Manager server and Agent are installed in
a Windows environment ................................................................................................. 394
15
7-b.1
7-b.2
7-b.3
7-b.4
7-b.5
7-b.6
Restore data for Hitachi Storage Command Suite products ................................. 396
7-b.7
Restore the definition information files for the Tuning Manager server . 396
7-b.8
Restore the definition information files for Performance Reporter .......... 398
7-b.8(ii)
7-b.10
7-b.11
Restore the definition information files for HTnM-Agent REST Services (Ver. 8.0 or
later)
401
7-b.12
Restore the performance data for Tuning Manager API (Ver. 8.0 or later) ............ 401
7-c.2
7-c.3
7-c.4
7-c.5
Back up data for Hitachi Storage Command Suite products ................................ 404
7-c.6
Back up the definition information files for the Tuning Manager server ............... 405
7-c.7
Back up the definition information files for Performance Reporter ...................... 406
7-c.7(ii) Back up the definition information files for Tuning Manager REST Application
Service (Ver.8.0 or later) ................................................................................................. 407
7-c.8
7-c.9
7-c.10
Back up the definition information files for HTnM-Agent REST Services (Ver.8.0 or
later)
410
7-c.11 Back up the performance data for Tuning Manager API (Ver.8.0 or later) ................. 410
7-c.12 Back up the Hybrid Store (Ver. 8.1.3 or later) .............................................. 410
7-d. Restore procedure on a host on which the Tuning Manager server and Agent are installed in
a UNIX environment .......................................................................................................411
7-d.1
Purpose ...........................................................................................................411
7-d.2
Prerequisites ....................................................................................................411
7-d.3
7-d.4
Terms ..............................................................................................................411
7-d.5
7-d.6
Restore data for Hitachi Storage Command Suite products ................................. 413
7-d.7
Restore the definition information files for the Tuning Manager server ................ 413
7-d.8
Restore the definition information files for Performance Reporter ....................... 414
7-d.8(ii)
7-d.10
7-d.11
Restore the performance data for Tuning Manager API (Ver. 8.0 or later)
418
Cases.............................................................................................................. 421
10-a.2
10-a.3
10-b Cases in which HTnM did not operate correctly due to an IPv6 loopback
address(ealier than 7.4.1) ............................................................................................................ 422
10-c
10-b.1
Cases.............................................................................................................. 422
10-b.2
10-b.3
The device information for an instance of RAID Map Agent started from a job
10-c.2
10-c.3
10-c.4
10-d Unable to launch HiRDB during the establishment of a cluster environment .................. 424
10-d.1
10-d.2
10-d.3
10-e.2
10-e.3
10-e.4
Appendix 11 Update of time zone information (HCS 7.0.1 or later) .......................................................... 428
11-a Obtaining tzupdater ............................................................................................................ 428
11-b Using tzupdater ................................................................................................................... 428
11-c Notes .................................................................................................................................... 432
Appendix 12 Actions to be taken when memory is insufficient................................................................... 433
12-a Actions to be taken when the jpcrpt command is unable to output information
because of insufficient memory ................................................................................................... 433
12-a.1
Cases.............................................................................................................. 433
12-a.2
12-a.3
12-b Actions to be taken when Main Console terminates abnormally during polling ............... 435
12-b.1
Cases.............................................................................................................. 435
12-b.2
12-b.3
Appendix 13 Recommended action when the KAVE00213-W message is output and when
performance data collection is skipped ......................................................................................................... 437
13-a Identifying the target for which the KAVE00213-W message is output ............................ 437
13-b Guide for specifying a value for the Collection Interval for records of the PI record
type
438
13-b.1
13-b.2
Appendix 14 Service IDs and service keys of the products ......................................................................... 441
14-a Service IDs and service keys specified when backing up and restoring the StoreDB........ 441
Appendix 15. Handling cases in which the host name was incorrectly changed (in V7.6.1 or
later) ................................................................................................................................................................. 442
15-a Overview .............................................................................................................................. 442
15-b Action to take if you cannot restore the old host name....................................................... 442
15-b.1 Action to take if the name of an HTnM server host was changed ............................. 442
15-b.2 Action to be taken if the name of an HTnM agent host was changed ........................ 446
15-c Using RAS information to check whether the host name was changed in the correct
manner 451
Appendix 16 Initializing the database (V8.0.1 or later) ............................................................................... 452
Appendix 17 Steps in a cluster environment without using commands ..................................................... 452
Appendix 18 Precautions when using Hybrid Store (Version 8.1.3 or later) ............................................. 453
18-a Procedure to change the data storage format from Hybrid Store to Store database ......... 453
Appendix 19 How to check the data storage format of Agent ..................................................................... 459
19-a How to check the data storage format of Agent (Version 8.1.3 to earlier than 8.2.1) ......... 459
18
19-b How to check the data storage format of Agent (Version 8.2.1 or later) ............................. 460
19
1.
Related Publications
The following lists the manuals related to Tuning Manager server. Check the latest version of manual
when you perform troubleshooting.
Table 1.1-1: English editions of Tuning Manager server manuals
Title
In Ver.6
Hitachi Tuning Manager Software Installation Guide
In Ver.7
Hitachi Command Suite Tuning Manager Software Installation Guide
In Ver.8
Hitachi Command Suite Tuning Manager Installation Guide
In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
In Ver.8
Hitachi Command Suite Tuning Manager API Reference Guide
In Ver.6
Hitachi Tuning Manager Software Users Guide
In Ver.7
Hitachi Command Suite Tuning Manager Software User Guide
In Ver.8
Hitachi Command Suite Tuning Manager User Guide
In Ver.6
Hitachi Tuning Manager Software Hardware Reports Reference
In Ver.7
Hitachi Command Suite Tuning Manager Software Hardware Reports Reference
In Ver.8
Hitachi Command Suite Tuning Manager Hardware Reports Reference
20
In Ver.6
Hitachi Tuning Manager Software Operating System Reports Reference
In Ver.7
Hitachi Command Suite Tuning Manager Software Operating System Reports Reference
In Ver.8
Hitachi Command Suite Tuning Manager Operating System Reports Reference
In Ver.6
Hitachi Tuning Manager Software Application Reports Reference
In Ver.7
Hitachi Command Suite Tuning Manager Software Application Reports Reference
In Ver.8
Hitachi Command Suite Tuning Manager Application Reports Reference
In Ver.6
Hitachi Tuning Manager Software Messages Reference
In Ver.7
Hitachi Command Suite Tuning Manager Software Messages Reference
In Ver.8
Hitachi Command Suite Tuning Manager Messages
In Ver.6
Hitachi Tuning Manager Software Command Line Interface Guide
In Ver.7
Hitachi Command Suite Tuning Manager Software CLI User Guide
In Ver.7.1 to earlier than 8.0
Hitachi Command Suite Tuning Manager Software CLI Reference Guide
In Ver.8
Hitachi Command Suite Tuning Manager CLI Reference Guide
In Ver.6
Hitachi Tuning Manager Software Getting Started Guide
In Ver.7
Hitachi Command Suite Tuning Manager Software Getting Started Guide
In Ver.8
Hitachi Command Suite Tuning Manager Getting Started Guide
In Ver.8
Hitachi Command Suite System Requirements
21
2.
2.1
General flowchart
Error
Yes
No
Did the error occur during
installation of Agent?
Yes
See 2.2.4. Error during installation of Agent
No
Did the error occur during
startup of a Tuning
Manager server service?
Yes
No
Did the error occur during
startup of an Agent service?
Yes
No
Is data displayed
correctly?
No
Yes
Data that must be collected:
If you cannot determine where
the error occurred, collect all
logs.
22
2.2.
Installation error
No
Yes
END .
No
Yes
Satisfy the requirements in Checks A, B,
C, D, E, F#8-2, G, H
Yes
No
#2
END .
1
23
No
Has Tuning Manager series
#9
been already installed ?
Yes
Check the file and folder that should be
located after installation by comparing with
[List of file and folder] in the manual. For
refereed manual, see Table 1.1-1.
- In Ver.6
Hitachi Tuning Manager Software Installation Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Installation
Guide
Note:
Even in Linux (x64), some of the prerequisite packages must
be the 32-bit versions. These prerequisite packages might also
have 64-bit versions under similar names. Check carefully to
make sure that the 32-bit packages are installed rather than the
64-bit versions.
24
#1
No
Yes
END .
Are Checks A#3, B#4, C#5, D#6,
E#7, F#8, G#9 and H#10
applicable?
No
Yes
Is
KATN00326-W message
output in log file#11
No
Perform
2.2.3.1.
Dealing with
zero-byte file
Yes
Re-installation of Tuning Manager server
Yes
No
#2
END .
#7 Check E (kernel parameter check)
If you install Tuning Manager server to Solaris operating system or
Linux operating system, make sure that kernel parameter values
satisfy Tuning Manager server requirements.
25
No
Yes
In Ver.8.0 or later
Hitachi Command Suite Tuning Manager Installation Guide
Changing a host name after starting operations
#11
Check if KATN00326-W message is output in the following
log file
Note:
Even in Linux (x64), some of the prerequisite packages must
be the 32-bit versions. These prerequisite packages might also
have 64-bit versions under similar names. Check carefully to
make sure that the 32-bit packages are installed rather than the
64-bit versions.
26
If installation of Tuning Manager fails, check if the KATN00326-W message is output in the trace
log file for installation, and in this case, perform the following procedure. When the KATN00326-W
message is output for hcmdssrv, perform the force uninstall of Tuning Manager server, and install
Hitachi Command Suite products including Tuning Manager server.
[Message]
KATN00326-W The following invalid empty files were detected at the installation destination of
Common Component:
< The name of Common Component command file detected zero byte >
27
[Recovery actions]
Necessary procdures are shown below when the message described above is output..
Confirm the version of the Common Component on the integrated installation media .#2
Success?#7
Yes
#1 How to confirm the version of the Common Component that have been installed
[In Ver.7.4.1 to earlier than 8.0.0]
- In Windows
Confirm the version by the key (a 6-digit numeric value) under the registry key shown below
indicating the version, revision, and fixed number.
(When
x86
is
applied)HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\HiCommand
28
Value
EXCurrentVersion
<Linux>
<HBase installation directory>/Base/sample/conf/build
(Example)
In the case when the version of the Common Component is V7.5.0
cat build
07500000
- In Linux
Confirm the version by referring to the build file shown below.
<HBase installation directory>/Base64/sample/conf/build
(Example)
In the case when the version of the Common Component is V8.0.0
cat build
08000000
#2 Confirm the version of the Common Component on the integrated installation media.
Refer the BUILD(or build) file which exists just under the stored directory of Common
Component on the integrated installation media to confirm the version of the Common Component
on it
29
The following is the stored directory of Common Component on the integrated installation media.
#
OS
Windows
Solaris(SPARC)
Linux(RHEL)
Linux(SUSE)
(Example)
In the case when the version of the Common Component on the integrated installation media is
V7.5.0
cat BUILD
07500000
Note: Check high 6 digit numeric value which shows the version, revision, and fixed number and
ignore 7, 8 digit numeric value.
#3 Confirm the result of version check at #1 and #2, and the numbers of high 6 digit numeric value
are identical.
Note: High 6 digit numeric value shows the version, revision, and fixed number and ignore 7, 8
digit numeric value.
- In Solaris,Linux
< Install directory of Common Component >/bin/hcmdssrv -stop
- In Solaris,Linux
< Install directory of Common Component >/bin/hcmds64srv -stop
30
- In Solaris,Linux
<Common-Component-installation-directory>/bin/hcmdssrv -statusall
- In Solaris,Linux
<Common-Component-installation-directory>/bin/hcmds64srv -statusall
#6 When executing the force installation of Common Component, move your current directory to the
stored directory of Common Component on the integrated installation media which is shown above
and execute it by the command as below.
- In Windows
HBinst.exe /ENFORCE /I <Common-Component-installation-directory>
- In Solaris
31
(*1,2)
Specify
the
directory
which
do
not
include
the
directory
"Base"
as
the
(Example)
In the case when performing the force installation of Common Component in Linux
#7 Check if the result of the forced installation of Common Component in the following way.
[In Ver.7.4.1 to earlier than 8.0.0]
-In Windows
Check if the exit code is zero by referring to a value of the registry below.
Registry
Key
Value
Productrtn
-In Solaris,Linux
Check if the exit code is zero by referring to the following file.
/tmp/hcmdsrtn.inst
(Example)
In the case when the forced installation of Common Component succeeded.
cat /tmp/hcmdsrtn.inst
0
32
(*2)
Productrtn
- In Linux
Check if the exit code is zero by referring to the following file.
/tmp/hcmds64rtn.inst
(Example)
In the case when the forced installation of Common Component succeeded.
cat /tmp/hcmds64rtn.inst
0
#8 See "Appendix 3 Tuning Manager Deletion Procedures" for procedure how to perform a force
uninstall of Tuning Manager server
33
Yes
No
Did a warning occur
during installation of the
Agent?
Yes
No
Yes
Collect the log.
#6
No
#13
Is Check K
applicable?
No
No
Yes
Yes
Check the file and folder that should be
located after installation by comparing with
[List of file and folder] in the manual. For
refereed manual, see Table 1.1-1.
END
Re-installation of Agent
Yes
Collect the log.
Collect the installation log#6.
Yes
No
Is Check K#13
applicable?
Yes
END
34
No
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Control\FileSystem
35
#10 Check H (Port number duplication check) (Agent for RAID V8.0.0 or later)
If the default port numbers of Tuning Manager API are used in other process, installation will fail. Check if the error message KDJE19310-E
java.net.BindException: Address already in use: JVM_Bind is not been output.
[Log files storage location]
For windows:
Suite-installation-directory\TuningManager\jp1pc\htnm\HBasePSB\CC\server\public\ejb\AgentRESTService\logs\cjexception*.log
For AIX, HP-UX(IPF), Linux:
/opt/jp1pc/htnm/HBasePSB/CC/server/public/ejb/AgentRESTService/logs/cjexception*.log
If the error message above has been output, change the port number used by other process. If you want to use the Agent without changing the port number
used in other process; stop the corresponding process, reinstall the Agent and then change the port number for the Agent(*1)(*2).
(*1) For instructions of changing port number, refer the following manual.
Hitachi Command Suite Tuning Manager Installation Guide
Configuring the port number
(*2) If this Check corresponded in VUP installation and then reinstallation was performed, the installation type displayed in the installer dialog will be
"Overwrite".
#11 Check I (Confirmation of IPv4 communication) (Agent for RAID V8.0.0 or later)
If the IPv4 communication is not configured in the installation target host, installation will fail.
Check if any of the following conditions meet:
(1) The network interface in operation does not exist.
(2) IPv4 address is not set in the network interface.
Note:
Even in Linux (x64), some of the prerequisite packages must be the 32-bit versions. These prerequisite packages might also have
64-bit versions under similar names. Check carefully to make sure that the 32-bit packages are installed rather than the 64-bit
versions.
#13 Check K (verification of the status of Hybrid Store) (Agent for RAID v8.1.3 or later, Agent for NAS v8.2.1 or later)
When the installation finishes, one of the following warning messages is displayed to prompt you to perform the settings to convert to
Hybrid Store databases.
(1) The conversion to Hybrid Store databases did not finishe. After the installation finishes, perform the settings to convert to Hybrid
Store databases, and then start operation.
(2) An attempt to convert to Hybrid Store databases failed. After the installation finishes, follow the action to be taken when the
htmhsmigrate command fails, and then perform the settings to convert to Hybrid Store databases. <command=htmhsmigrate,
rc=command-return-value>
If these messages are displayed, apply the following workaround:
[Workaround]
See the Hitachi Command Suite Tuning Manager Agent Administration Guide, and then manually migrate the data and perform the
settings to convert to Hybrid Store databases.
Agent for RAID and Agent for NAS cannot be operated until you have performed the settings to convert to Hybrid Store database
(instances cannot be started).
Note that if you perform a re-installation before performing the settings to convert to Hybrid Store database, the warning message will
be displayed again to prompt you to perform the settings to convert to Hybrid Store database when the installation is finished.
Note:
The warning messages above will be displayed when one of the following conditions is met:
(1) At the time of the upgrade installation, you selected Hybrid Store database and then the [Inherit performance data after installation]
option.
(2) At the time of the new or upgrade installation, you selected Hybrid Store database and then an attempt to convert to Hybrid Store
databases within the installer failed.
36
2.3.
No
Yes
#1
No
#2
Are Checks A ,B ,
C#3, #4and D#5
Yes
Satisfy the requirements in Checks A , B, C, D.
No
- In Ver.7
- In Ver.8
Yes
Yes
No
No
Yes
Satisfy the requirements in Checks E, F, G.
37
No
No
Yes
Yes
END
Satisfy the requirements in Checks H, I.
Yes
No
END
Figure 2.3.2-1 Error during startup of a Tuning Manager server service flow
Check item
Account information
Description
To use the jpcstart command to start the Agent service, you must have logged on
with the following account:
- Windows: A member of the Administrators group
- Unix: Root
Agent Store must be started before you can start Agent Collector. Use the jpcctrl list
command to make sure that Agent Store is running. For details about how to use the
jpcctrl list command, see 2.4.2.
If you use Windows SCM to start the Agent Collector service that is running on the
same host as for Collection Manager, the Agent Collector service cannot start unless
the Master Store service is running. Use the jpcctrl list command to make sure that
Master Store is running. For details about how to use the jpcctrl list command, see
2.4.2.
Check the jpclog whether error message is out put or not. And then see manual of
Hitachi Tuning Manager or FAQ document contained in Hitachi Tuning Manager
Log analysis guide, do the action that corresponds to the message.
Note that some Agents stop the service if an attempt to check the connection with the
monitoring target resource has failed during startup of the service.
target)
Resource type
has failed
Command and Library
In-band/
After the
Out-band
service
service
started
Platform Agent
Server &
storage
and so on
Server
(Windows)
In-band
--
Continues the
Agent
--
Note 1
--
--
SNM API
Out-band
--
In-band
--
In Ver.7.1 to 7.6.1:
Out-band
Fails
service.
Platform Agent
Server
(Unix)
OS commands,
system calls, and so on
RAID Agent
Thunder
(Thunder, AMS,
storage
HUS100)
RAID Agent
Lightning
(Lightning, USP)
storage
Switch Agent
Brocade switch
(Brocade(DCFM
(B-Model)
and
or later))
Brocade switch
Windows/Solaris/Linux:SMI-S
In Ver.8.0 or later:
to
start
the
Windows/Linux: SMI-S
(M-Model)
39
Switch Agent
Brocade switch
(B-Model)
earlier))
In Ver.6.0:
Out-band
Windows: SMI-S
2.3.3.1.2.
(Brocade API)
In Ver.6.1 to 7.0:
Windows/Solaris: SMI-S
Switch Agent
Brocade switch
(Brocade(SMI Agent
(B-Model)
In Ver.7.1 to 7.6.1:
Out-band
Windows/Solaris/Linux: SMI-S
In Ver.8.0 or later:
later))
2.3.3.1.2.
Windows/Linux: SMI-S
Switch Agent
Brocade switch
(M-Model)
or earlier))
In.Ver.6.0 to 6.1:
Out-band
Windows/UNIX: SWAPI
(McDATA API)
2.3.3.1.3.
In Ver.6.2 to 7.0:
Windows/Solaris: SMI-S
Switch Agent
Brocade switch
(Brocade(SMI Agent
(M-Model)
Out-band
Windows/Solaris/Linux: SMI-S
In Ver.8.0 or later:
later))
Switch Agent
In Ver.7.1 to 7.6.1:
2.3.3.1.3.
Windows/Linux: SMI-S
CISCO switch
In Ver.6.0
Out-band
Windows: SMI-S
earlier))
In Ver.6.1 to 7.0:
2.3.3.1.4.
Windows/Solaris: SMI-S
Switch Agent
CISCO switch
CISCO(Seed Switch)
In Ver.7.1 to 7.6.1:
Out-band
Windows/Solaris/Linux: SMI-S
In Ver.8.0 or later:
2.3.3.1.4.
Windows/Linux: SMI-S
Switch Agent
CISCO switch
CISCO(DCNM-SAN
(DCNM-SAN
SMI-S Agent)
7.2.1 or later))
Oracle Agent
In Ver.7.2.1 to 7.6.1:
Out-band
Windows/Solaris/Linux: SMI-S
In Ver.8.0 or later:
2.3.3.1.5.
Windows/Linux: SMI-S
Oracle database
OCI
--
SQL Agent
SQL Server
ADO
--
database
DB2 Agent
DB2
DB2
Universal
Management API
Database
--
Fails
to
start
the
40
NAS Agent
NAS
NAS commands
Out-band
--
Exchange Agent
Exchange
--
Fails
Server
to
start
the
HealthCheck Agent
--
--
--
EAP Agent
SAP system
--
--
Note 1. To start a Platform Agent (for Windows) service, the following service must be running:
Service name: Remote Registry Service
Note that the Platform Agent service cannot start if the above service remains inactive due to, for
example, the security policy.
41
2.3.3.1.1.
Errors during startup of the Switch Agent service (when using Brocade (DCFM SMI
Agent) instances to monitor Brocade switches (7.1 or later))
No
Make sure that the services for DCFM and DCFM SMI
Agent are running.
End
Yes
No
Yes
Satisfy the requirements in Agent common check.
Yes
No
No
End
Yes
Satisfy the requirements in Checks A to D.
No
Yes
Go to the next page.
End
#5 Check D (Java VM being installed check)
Switch Agent uses SMI-S, and uses Java VM
environment. This environment check is done in the
startup procedure of Switch Agent.
42
#6
Figure 2.3.3.1.1-1 Error during startup of the Switch Agent service flow
(when using Brocade (DCFM SMI Agent) instances to monitor Brocade switches (7.1 or later))
2.3.3.1.2.
Errors during startup of the Switch Agent service (when using Brocade instances (7.0 or
earlier) or Brocade (SMI Agent for FOS) instances (7.1 or later) to monitor Brocade
B-Model switches)
#1 Agent common check
See Table 2.3.3.1-1.
No
Yes
2
Is Agent common check#1
applicable?
No
Yes
Satisfy the requirements in Agent common check.
No
Yes
43
No
Yes
Satisfy the requirements in Check A.
No
Yes
Collect the logs#3.
44
Is Performance Reporter
displaying information on
the monitored switches? #4
Yes
End
No
No
Is monitoring by Switch Agent
supported for the switches for
which information is not
displayed?
End
Yes
Yes
No
No
Is the Switch Agent version 7.1 or later?
Yes
Upgrade Switch Agent to a version that
supports the switch OUI code for which
information is not displayed.
Is Performance Reporter
displaying information on
the monitored switches? #5
Yes
No
Figure 2.3.3.1.2-1 Error during startup of the Switch Agent service flow
(when using Brocade instances (7.0 or earlier) or Brocade (SMI Agent for FOS) instances (7.1 or
later) to monitor Brocade B-Model switches)
45
2.3.3.1.3.
Error during startup of the Switch Agent service (when using McDATA instances (7.0
or earlier) or Brocade (SMI Agent for EOS) instances (7.1 or later) to monitor Brocade
M-Model switches)
#1 Agent common check
See Table 2.3.3.1-1.
No
Yes
No
Yes
Satisfy the requirements in Agent common check.
Note: Make sure that the version and build number for
DCFM/EFCM-Client match those of
DCFM/EFCM-Server.
Yes
No
Are Checks A#2, B#3, C#4,
D#5 and E#6 applicable?
No
Yes
Satisfy the requirements in Checks A to D.
No
Yes
Go to the next page.
46
47
switches is displayed.
Is Performance Reporter
displaying information on
the monitored switches?#8
Yes
End
No
No
End
Yes
Yes
No
No
Is the Switch Agent version 7.1 or later?
Yes
Upgrade Switch Agent to a version that
supports the OUI code of the switch for
which information is not displayed.
Is Performance Reporter
displaying information on
the monitored switches? #8
Yes
No
Figure 2.3.3.1.3-1 Error during startup of the Switch Agent service flow
(when using McDATA instances (7.0 or earlier) or Brocade (SMI Agent for EOS) instances (7.1 or later)
to monitor Brocade M-Model switches)
48
2.3.3.1.4.
Error during startup of the Switch Agent service (when using CISCO instances (7.0 or
earlier) or CISCO (Seed Switch) instances (7.1 or later) to monitor Cisco switches)
#1 Agent common check
See Table 2.3.3.1-1.
No
Yes
End
No
Yes
Satisfy the requirements in Agent common check.
No
Yes
No
No
End
Yes
Satisfy the requirements in Check A, B
No
Yes
Collect the logs#4.
End
Figure 2.3.3.1.4-1 Error during startup of the Switch Agent service flow
when using CISCO instances (7.0 or earlier) or CISCO (Seed Switch) instances (7.1 or later) to monitor
Cisco switches)
49
2.3.3.1.5.
Error during startup of the Switch Agent service (when using CISCO(DCNM-SAN
SMI-S Agent) instances (7.2.1 or later) to monitor Cisco switches)
#1 Agent common check
See Table 2.3.3.1-1.
No
Yes
End
No
Yes
#3 Check B (Java VM being installed check)
Switch Agent version 7.2.1 or later for Windows/Linux
and uses SMI-S, and version 7.2.1 to earlier than 8.0.0 for
Solaris uses Java VM environment. This environment
check is done in the startup procedure of Switch Agent.
No
Yes
No
No
End
Yes
Satisfy the requirements in Check A to C
No
Yes
Collect the logs#5.
End
Figure 2.3.3.1.5-1 Error during startup of the Switch Agent service flow
when using CISCO(DCNM-SAN SMI-S Agent) instances (7.2.1 or later) to monitor Cisco switches)
50
2.3.3.1.6.
No
Yes
END
No
Yes
Satisfy the requirements in Agent common check.
Yes
No
No
Yes
Satisfy the requirements in Checks A to C.
END
No
Yes
Collect the logs#5.
END
Figure 2.3.3.1.6-1 Error during startup of the Oracle Agent service flow
51
2.3.3.1.7.
No
Yes
END
No
Yes
Satisfy the requirements in Agent common check.
Yes
No
Are Checks A#2 and B#3
applicable?
No
For details about how to update instance information or
how to delete instance/create instance, see the manual
for SQL Agent.
Yes
#4 About the logs
Obtain the logs for SQL Agent.
You do not need to obtain information about Main
Console, HBASE, Collection Manager,
InterBase/HiRDB.
We recommend you use the jpcras command to collect
maintenance information.
For details about how to use the jpcras command, see
4.1.5. jpcras command.
No
Yes
Collect the logs#4.
Figure 2.3.3.1.7-1 Error during startup of the SQL Agent service flow
52
2.3.3.1.8.
No
Yes
END
No
Yes
Satisfy the requirements in Agent common check.
Yes
No
No
Yes
Satisfy the requirements in Checks A, B and C.
END
Did the service
fail to start?
No
Yes
Collect the logs#5 #6.
Figure 2.3.3.1.8-1 Error during startup of the DB2 Agent service flow
53
2.3.3.1.9.
No
Yes
END
No
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Exchange\Setup
Yes
Yes
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Exchange\v8.0\MailboxRole
No
No
Is Check A#2 applicable?
#3 About the logs
Obtain the logs for Exchange Agent.
You do not need to obtain information about Main
Console, HBASE, Collection Manager,
InterBase/HiRDB.
We recommend you use the jpcras command to collect
maintenance information.
For details about how to use the jpcras command, see
4.1.5. jpcras command.
Yes
Satisfy the requirements in Checks A.
END
Did the service
fail to start?
No
Yes
END
Figure 2.3.3.1.9-1 Error during startup of the Exchange Agent service flow
54
Check item
Description
To use the jpcstart command to start the Agent service, you must
have logged on with the following account:
- Windows: A member of the Administrators group
- Unix: Root
If you use Windows SCM to start the Agent Collector service that is
Master Store running status
running on the same host as for Collection Manager, the Agent
Collector service cannot start unless the Master Store service is
running. Use the jpcctrl list command to make sure that Master
Store is running. For details about how to use the jpcctrl list
command, see 2.4.2.
Free space in the disk for
Check the amount of free space in the disk for storing the Agent
storing the Agent Store
Store database. If the disk is full, Agent Store cannot start. For
details about how to change the location to store the Agent Store
database
database, see the following manual:
- Ver.6
Hitachi Tuning Manager Software User's Guide
- Ver.7
Hitachi Command Suite Tuning Manager Software User Guide
- Ver.8
Hitachi Command Suite Tuning Manager User Guide
Check
the jpclog whether error message is out put or not. And then
Common
message
log
see manual of Hitachi Tuning Manager or FAQ document contained
(jpclog)
in Hitachi Tuning Manager Log analysis guide, do the action that
corresponds to the message.
Account information
55
No
Yes
End
No
Yes
Satisfy the requirements in Agent common check.
Yes
No
END
56
No
Yes
Has the Agent started in the
#1
Stand Alone mode?
No
End
Yes
Are Checks A#2 , B#3
and C#4 applicable?
No
Yes
Satisfy the requirements in Checks A, B and C.
#5
57
No
Yes
End
#5
Figure 2.3.3.3-1 Error during connection between Collection Manager and Agent flow
58
2.3.4. Error during startup of Tuning Manager REST service (Ver. 8 or later)
Check the log
No
Yes
END
(Running normally)
No
Yes
(#1)
<Check>
Is HTnM REST Application Service not running?
<Action>
If it isnt running, start the service using the following command.
<Common-Component-installation-directory>\bin\hcmds64srv /start /server TuningManagerRESTService
Note: In the case of UNIX, replace /to - in the command options.
(#2)
<Check>
Is it right after HTnM REST Application Service has started? If it is done right after HTnM REST Application Service
has started, there is a possibility that there is no output because of internal process.
<Action>
After a while, check the log. (It takes a few minute)
(#3)
< Check>
Is the error message output to the message log?
< Action>
Take action of the following message:
See "4. API Messages" and "List of Output Destinations for Messages" of "Tuning Manager API Reference Guide".
(#4)
Collect Tuning Manager Server log, in addition to the collection target log of the previous section(*).
(*) 2.3.2 Error during startup of a Tuning Manager server service (Ver. 6 or later)
Figure 2.3.4-1 Error during startup of Tuning Manager REST Application Service flow
59
<Legend>
No
Question
Yes
Figure 2.3.4-2 Connection to Tuning Manager REST Service from client API flow
60
2.4.
#1
No
#1 Polling status check
Make sure that Main Console has performed
polling to the Agent.
Yes
Are Checks A#2 and
B#3 applicable?
No
Yes
Satisfy the requirements in Checks A and B.
Yes
No
Yes
No
Collect the logs#10.
See 2.3.3.3.
Contact the support center and
ask for investigation.
Perform polling#5.
#4 Checking the Agent recognition in Collection
Manager
Execute the jpcctrl list command to make sure that
the Service ID of the Agent is displayed.
#5 Performing Polling
If you want to quickly check the result of polling, we
recommend you perform polling manually.
To perform polling manually, in the Data Polling
window of Main Console, click the Start Polling
button.
61
Yes
Is polling to
Agent#6 successful?
No
Yes
Yes
Satisfy the requirement in Check D.
No
No
Is Check D#7
applicable?
No
Does n/a appear for
a metric?
End
Yes
#12
Is Check F#9,
applicable?
Yes
No
Contact the support center
and ask for investigation.
Has Agent Store
started?
No
No
See 2.3.3.1.
Yes
See 2.3.3.2.
Yes
End
No
Can PR display a
real-time report?
Yes
See 2.4.4.1.
62
Figure 2.4-1 Tuning Manager server error causing n/a display for data flow
63
64
65
In Main Console, choose System Reports and select a Polling Time to open the Polling Details
window. In this window, you can check the Last Recorded Time field for each Agent to see whether
polling to the Agent was successful.
Note: The Last Recorded Time field displays the time information for the latest data stored in
HiRDB. In the Agents Status window opened from Polling Status, the Last Recorded Time field
shows data for individual Agents. You can check the update status of these values to see whether
the data is successfully collected from the Agents using polling.
Figure 2.4.2.3-2: Checking the Last Recorded Time in the Polling Details window
66
Error
Remarks
See 2.3.3.1.
The Agent Collector service is running, but has failed to collect data from the
See 2.4.5.2.
Error isolation:
An error shown in No. 1 or 2 or 4 in Table 2.4.4.1-1 may have occurred.
Error
Remarks
See 2.3.3.2.
The service of Agent Store stopped during the period of time for
See 2.3.3.2.
During the period of time for which you attempted to display data in
See 2.3.3.1.
the report, the service of Agent Store was running but the service of
As
with
this
error,
such
delay,
the
KAVE00166-W message is
output
to
log.
To
During the period of time for which you attempted to display data in
See 2.4.5.2.
the report, the service of Agent Collector failed to collect data from
the resources being monitored.
5
in Agent Store.
Method:
Use PR to display the Agent history data for instance Brocade A.
Data for the number of bytes received at the switch is stored in the following records:
- Configuration information for the port: Switch Agent/PD_SWS record
Create and display a report showing the history data for the PD_SWS record.
Result:
The history report does not contain the data of the period of time from 13:00 in December 7,
2004 to 08:00 in December 8, 2004. The report contains data earlier than 13:00 in December 7,
2004 or later than 08:00 in December 8, 2004.
Error isolation:
An error shown in No. 2 or 3 in Table 2.4.4.2-1 may have occurred.
Agent operates depending on the system clock of the host on which it is installed. If the system
clock of the machine containing Agent is behind the system clock of the machine running Tuning
Manager server, data collection from Agent may delay during the specified polling time.
The following example shows the case where Main Console does not display the Agent data
because the system clock of the host running Agent is behind the system clock of the host running
Tuning Manager server.
Example:
Conditions:
Tuning Manager products running on host A: Tuning Manager server and Agent A
System clock of host A: 2004/12/08 13:00
Tuning Manager server on host A has been running from 11:50 in December 8, 2004.
In host A, the scheduled polling is set to 13:00 and 14:00 in Main Console.
Polling results:
Tuning Manager server performed the first polling when the system clock of host A reached
2004/12/08 13:00.
After the polling finished, Main Console displayed data of Agent A running on host A, but
70
The second polling collected the following records from the Agents:
Host A: Records at 2004/12/08 12:00 (Data aggregation for the PI-type record completed.)
Records at 2004/12/08 13:00 (Data aggregation for the PI-type record completed.)
Records at 2004/12/08 14:00 (Data aggregation for the PI-type record is
incomplete.)
Host B: A record of 2004/12/08 12:00 (Data aggregation for the PI-type record
completed.)
Records at 2004/12/08 13:00 (Data aggregation for the PI-type record is
incomplete.)
Note: Since the host B clock did not reach 14:00 at the second polling, a record of
14:00 did not exit in Agent Store.
As a result, the records at 2004/12/08 13:00 collected from Agent A on host A and the
records at 2004/12/08 12:00 collected from Agent B on host B are stored in InterBase or
HiRDB during the second polling.
71
2.4.5.2. Unsuccessful data collection from the resources being monitored by Agent Collector
If Main Console displays n/a for metrics because of an unsuccessful attempt to collect data from the
resources being monitored by Agent Collector, see the FAQ.
If you cannot correct the problem according to the FAQ, use the jpcras command to acquire the
Agent log and database. Then contact the Support Center.
72
Symptom
Assumed factors
(1) If there is KATR11002-E output in the message log;
Collection Manager is stopped. Start the service in
reference to "1-10 Starting and stopping Collection
Manager and Agent services" of "Tuning Manager Agent
Administration Guide".
service.
or null remains).
3
Symptom
Assumed factors
74
3.
To correctly notify the Support Center of the situation where the error occurred, report all the
following mandatory information:
Mandatory information to be reported
(1) Phenomenon
(2) Occurrence time
(3) System configuration diagram (Server, storage, switches, SMTP server, database network
configuration, Tuning Manager server configuration, and Agent configuration)
(4) Operation details (displayed windows, clicked buttons, and executed commands)
(5) Reproducibility (whether the error occurs again in the same situation)
(6) Data acquired using the applicable RAS information collection command
For details about how to use RAS information collection commands, see 4.1.
(7) System Log
(7.1) In Windows:
Contents of System Log and Application Log in the Event Viewer window (in Windows only)
(7.2) In UNIX:
syslog
(8) Operating system information (in Windows only)
- In Windows 2000:
Contents of System Information in Computer Management or System Information in
System Tools in Accessories
- In Windows Server 2003 and Windows Server 2008:
Contents of System Information in System Tools in Accessories
- In Windows Server 2012:
Contents of System Information in Administrative Tools or All apps
(9) Screenshots
Take the following screenshots:
(9.1) The window that you were operating when the error occurred (if an application error occurred)
(9.2) The error message dialog box
If there is detailed information, also take its screenshot.
(9.3) The entered command line and message output on the console (if an error
occurred during command execution)
For an error in the Agent for the logical host in a cluster configuration, collect the following
information:
(10) Information about the cluster software
When the cluster software is used to start or stop Agent, or to perform a failover, information
about the cluster software is needed to identify where (cluster software or Agent) the error
occurred.
75
Collect the trace information about the control (start, stop, etc.) requests from the cluster
software to Agent, and their results.
(11) Collect the information items (6), (7), and (8) on both the primary and secondary hosts. Note
that shared disk is mounted to the host when you execute the RAS command in the Active host
of Active-Standby cluster system.
If conversion of the CSV report format by using the htm-csv-convert command fails, the following
data must be obtained:
(13) The input file specified in htm-csv-convert
When the problems occurred in the jpctdraidperf command execution, the following data must be
obtained:
(14) The CSV file which jpctdraidperf command outputs
When the problems occurred in the htmrest command execution, the following data must be
obtained:
(15) Contents of standard output and standard error output obtained when specifying the --debug
option to execute the command.
The following is an example of the command executed when the --debug option is specified.
Example:
htmrest GET http://localhost:22015/DeviceManagerWebService/analytics/v1/objects/alert
-defs -u user -p password --debug > C:\tmp\htmrest_result.txt 2>&1
76
4.
RAS Collection
4.1.
Table 4.1-1 lists the products and commands for collecting RAS information of Tuning Manager
server.
Table 4.1-1:
Agent
Product
htm-getlogs
htm-
earlier
V7.0 to
V8.0
earlier
V7.0 to
V8.0
than
earlier
or
than
earlier
or
V7.0
than 8.0
later
V7.0
than 8.0
later
jpcprras
jpcras
dump
hinstgetlogs
V8.1.4 or
later
Main Console
Performance Reporter
Tuning Service#3
Y#4
Y#4
HBASE
Y#1
Y#1
Y#1
HiRDB
Collection Manager
Installer
Agent Collector
Y#2
Y#2
Agent Store
Installer
Legend:
Y: The command collects RAS information about this product.
N: The command does not collect RAS information about this product.
#1
Note that though jpcprras command gathers log files HBASE, it does not gather log files of HiRDB included
in HBASE. And htm-getlogs command also does not gather log files of HiRDB because it internally
executes jpcprras command. To gather the log files of HiRDB, please use hcmdsgetlogs command.
#2
The size of log files to be collected might become very large because RAS information on Agent store
includes Store database. Tuning Manager server version 6.4.0 provides the function to exclude Store
database from RAS information to be collected(secret option). For details, see 4.5 The problems in
acquiring RAS information and the contingency plan. (Ver.6.4 or later)
#3
In version 7.1 or later, Tuning Service collects RAS information for Windows and Solaris. However, it does
not collect RAS information for Linux because Linux does not support Tuning Service.
#4
77
The RAS information cannot be sent to Software division or it takes long time to send the RAS
information.
When Tuning Manager server 7.0.0-00 or later is used, if HTnM server and HTnM Agents are
installed on a same host, please execute jpcras command after executing hcmdsgetlogs command.
(2) Prerequisites
- To execute this command, you must have logged on as a member of the Administrators
group, root, or the equivalent.
- This command must be executed on a machine where Tuning Manager server is
installed.
- You do not need to stop the Tuning Manager server services. But, if the hcmdsgetlogs command is
executed during polling by the Tuning Manger server, export of HiRDB data may fail, resulting in
data collection not being completed. If this happens, data collection may be requested again as
necessary.
- To acquire the database information about Tuning Manager Agent, the Agent services
must be stopped.
(3) Use
For details about how to use this command, see the manual.
Example:
[ In Ver.6 to earlier than 8 ]
In Windows:
Suite-installation-directory\Base64\bin\hcmdsgetlogs /dir C:\Logs
In Solaris:
# /opt/HiCommand/Base/bin/hcmdsgetlogs -dir /export/Logs
In Linux:
78
# <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin/hcmdsgetlogs -dir
/export/Logs
[ In Ver.8 or later ]
In Windows:
Suite-installation-directory\Base\bin\hcmds64getlogs /dir C:\Logs
In Linux:
# <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin/hcmds64getlogs
-dir /export/Logs
Notes:
-
In Tuning Manager Ver.8.1.4 or later, if the hcmds64getlogs command shown above does not
exist, execute the hinstgetlogs command. For details about the hinstgetlogs command, see the
Hitachi Command Suite Software Troubleshooting Guide.
Note that hinstgetlogs is an open tool for the Support Center.
The data acquired using the hcmdsgetlogs or the hcmds64getlogs command is saved in an
archive file with the extension .jar.
The .jar archive files can be unpacked using the jar command included in J2SDK.
Since J2SDK is included in the Hitachi Storage Command Suite Common Component, on a
Windows machine where Tuning Manager server is installed, you can unpack the .jar archive
files by executing the following command:
[ In Ver.6 to earlier than 8 ]
> "C:\Program Files\HiCommand\Base\jdk\bin\jar.exe" -xvf path-name
[ In Ver.8 or later ]
> "C:\Program Files\HiCommand\Base64\uCPSB\jdk\bin\jar.exe" -xvf path-name
In the above, path-name is the path name of the HiCommand_log.jar file.
The compression format of .jar files is the same as the ZIP format. Therefore, you may be able
to use unzip software to unpack .jar files by changing the extension from .jar to .zip. Note that,
in this case, the archive files may be unpacked incorrectly.
might need a large disk capacity. You must be especially careful if the Store database size for Agent
or Tuning Manager is large. This chapter describes how to estimate the total capacity of the log
output destination, which is required for the common component, HiRDB, and HTnM when
executing the hcmdsgetlogs command.
(4.2) Overview
When you execute the hcmdsgetlogs command, the following four files are created. If you
specify a file name in the arc option and then execute the command, the HiCommand_log part
becomes the specified name.
Table 4.1.1-1: Files created by executing the hcmdsgetlogs command
#
Files
Major contents
HiCommand_log.jar
HiCommand_log.hdb.jar
HiCommand_log.db.jar
Database file
HiCommand_log.csv.jar
(4.3) Terms
The following terms are used in this section.
Table 4.1.1-2: Terms used in this chapter
#
Terms
Directory
Common-Component-installation-directory
(x86)
%SystemDrive%\Program Files\HiCommand\TuningManager
For Windows Server 2003 (x64), Windows Server 2008 (x64)
80
Files
(x86)\HiCommand\TuningManager
[ In Ver.8 or later ]
%SystemDrive%\Program Files\HiCommand\TuningManager
Value substituted
Calculation
Procedure
[A]
See (4.5)
[B]
See (4.6)
[C]
See (4.7)
[D]
See (4.8)
81
Table 4.1.1-4: Formula for estimating the HiCommand_log.jar size before compression
Calculating formula
[A] = [a] + [b] + [c] + [d] - [e] - [f] - [g] - [h]
* Substitute the following sizes for [a], [b], [c], [d], [e], [f], [g] and [h], respectively.
Variable
Value substituted
Calculation
Procedure
[a]
The size of the common component, the HTnM Install directory, and other
See (4.5.1)
directories
[b]
See (4.5.2)
[c]
See (4.5.3)
[d]
The size of RAS information for the Agent for RAID, installed on the same
See (4.5.4)
See (4.5.5)
[f]
See (4.5.6)
[g]
See (4.5.7)
[h]
See (4.5.8)
(4.5.1)
Estimating [a]: the size of the common component, the HTnM installation directory, and
other directories
[a] indicates the total sum of the directory sizes shown in Table 4.1.1-5.
Table 4.1.1-5: Common component, the HTnM Installation directory, and other directories
#
Windows
Common-Component-installation-directory
Tuning-Manager-server-installation-directory (*1)
Log output directory specified by the config.xml file for PerformanceReporter (If not specified,
3
Tuning-Manager-server-installation-directory\PerformanceReporter\log)
4
Solaris
/opt/HiCommand/Base
/var/opt/HiCommand/Base
/opt/HiCommand/TuningManager
/var/opt/HiCommand/TuningManager
/opt/jp1pc (*1)
Log output directory specified by the config.xml file for PerformanceReporter (If not specified,
6
/opt/HiCommand/TuningManager/PerformanceReporter/log)
7
82
Linux
<Hitachi-Command-Suite-Common-Component-Installation-directory>
/var<Hitachi-Command-Suite-Common-Component-Installation-directory>
<TuningManager-Installation-directory>
/var<TuningManager-Installation-directory>
/opt/jp1pc (*1)
Log output directory specified by the config.xml file for PerformanceReporter (If not specified,
6
<TuningManager-Installation-directory>/PerformanceReporter/log)
7
* The logical host environment directory is the directory that is specified while setting up the
logical host environment. This directory exists only when Tuning Manager server is configured
as the logical host mode.
(*1) In Ver.7.0 or later, or Ver.6.4 (do not collect Agent Store DB), do not include the capacity
of the following folders.
<Windows>
Tuning-Manager-server-installation-directory\jp1pc\<Service Key of Agent>\store
<UNIX >
/opt/jp1pc/<Service Key of Agent>/store
(4.5.2)
How to confirm the size of the syslog is different between Windows and UNIX.
See (4.5.2-1) for Windows, (4.5.2-2) for Solaris, (4.5.2-3) for Linux.
83
Files
/var/adm/messagesX *1
(*1) The last character X indicates the number.
Files
/var/log/messages[.X]
(*1) The last character X indicates the number.
(4.5.3)
Make sure to only execute this item in Windows Server 2003. [c] indicates the total sum of the
following file sizes:
Table 4.1.1-7: Watson log
#
(4.5.4)
Files
Estimating [d]: the size of RAS information for the Agent for RAID
(4.5.5)
Confirms the size directory, which is the destination of database file used by the common
component.
(4.5.5.1)
(4.5.5.2)
[For Windows]
- In Ver.6 to earlier than 8
<Common-Component-installation-directory>\bin\hcmdsdbpath
- In Ver.8 or later
<Common-Component-installation-directory>\sbin\hcmdsdbpath
[For Solaris]
85
/opt/HiCommand/Base/bin/hcmdsdbpath
[For Linux]
- In Ver.6 to earlier than 8
<Hitachi-Command-Suite-Common-Component-Installation-directory>/bin/hcmdsdbpath
- In Ver.8 or later
<Hitachi-Command-Suite-Common-Component-Installation-directory>/sbin/hcmdsdbpath
Output example
SYSTEM C:\Program Files\HiCommand\Base\database
HBASE_RDAREA C:\Program Files\HiCommand\Base\database\BASE\HF
HDVM_RD
C:\Program
Files\HiCommand\DeviceManager\HiCommandServer\database\DeviceManager\RD_HDVM
HTNM C:\Program Files\HiCommand\TuningManager\database\TuningManager\TM00
(4.5.5.3)
If the directory displayed after SYSTEM exists in one of the directories listed in
Table 4.1.1-5, [e] indicates the >\SYS size of the directory displayed after <SYSTEM (the
size of C: \Program Files\HiCommand\Base\database\SYS for the command
execution result shown above) If the directory does not exist in any of directories listed in
Table 4.1.1-5, [e] is 0.
(4.5.6)
Estimating [f]: the size of the installation directories for HiRDB and jdk
Windows
Common-Component-installation-directory\HDB
[ In Ver.6 to earlier than 8 ]
Common-Component-installation-directory\jdk
2
[ In Ver.8 or later ]
Common-Component-installation-directory\uCPSB\jdk
3
Common-Component-installation-directory\jdk1_4_02
Solaris
/opt/HiCommand/Base/HDB
/opt/HiCommand/Base/jdk
Linux
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
[ In Ver.6 to earlier than 8 ]
<Hitachi-Command-Suite-Common-Component-Installation-directory>/jdk
[ In Ver.8 or later ]
86
<Hitachi-Command-Suite-Common-Component-Installation-directory>/uCPSB/jdk
(4.5.7)
(4.5.7.2)
Output example
KATN01314-I The command htm-db-status will now be executed.
Database Capacity (Used/Total): 74920 / 2048000 kBytes
Area Path:
C:\Program Files\HiCommand\TuningManager\database\TuningManager\TM00
KATN01309-I The database status has been displayed.
(4.5.7.3)
Calculating formula
[g]= (Number of files, from the list of files that follows the Area Path: for the execution result of (4.5.7.2),
that exist in one of the directories listed in Table 4.1.1-5) * 2048000 kBytes
(4.5.8)
Estimating [h]: the size of the backup files for CollectionManager and Agent
[h] indicates the total sum of the backup file sizes for CollectionManager and Agent in the
directories listed in Table 4.1.1-5. The default backup destination directory is indicated in Table
4.1.1-9. Note that even if the backup destination directory is other than the default destination
directory, the size must be included as the calculation target when the backup destination
directory is under the directory listed in Table 4.1.1-5.
Table 4.1.1-9: The default backup destination directory for CollectionManager and Agent
#
Windows
Tuning-Manager-server-installation-directory\jp1pc\mgr\store\backup
3
Name>\backup
87
UNIX
opt/jp1pc/mgr/store/backup
Value substituted
Calculation
Procedure
(4.6.1)
[i]
See (4.6.1)
[j]
See (4.6.2)
Estimating [i]: the total sum of the capacities indicated by the pdinfoget - m command
(4.6.1.1)
(4.6.1.2)
How to set the environmental variable is different between Windows and UNIX.
See (4.6.1.2-1) for Windows, (4.6.1.2-2) for Solaris,(4.6.1.2-3) for Linux.
(4.6.1.2-1)
For Windows
<Step1> Execute the following command for setting the environmental variable
#
Command
cd /d "Common-Component-installation-directory\HDB\bin"
pdntcmd
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
#
Command
set PDDIR
(4.6.1.2-2)
For Solaris
<Step1> Execute the following command for setting the environmental variable
Depending on the type of shell, how to set the environmental variable differs.
#
Value
PDDIR
/opt/HiCommand/Base/HDB
88
PDCONFPATH
/opt/HiCommand/Base/HDB/conf
LD_LIBRARY_PATH
/opt/HiCommand/Base/HDB/lib
PATH
/opt/HiCommand/Base/HDB/bin
kind of shell
bash
source /opt/HiCommand/Base/HDB/bin/pduxenv
sh
PDDIR=/opt/HiCommand/Base/HDB
PDCONFPATH=/opt/HiCommand/Base/HDB/conf
LD_LIBRARY_PATH=/opt/HiCommand/Base/HDB/lib
PATH=/opt/HiCommand/Base/HDB/bin:$PATH
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
export PATH
csh or tcsh
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
#
Command
Display result
PDDIR=/opt/HiCommand/Base/HDB
(4.6.1.2-3)
<Step1> Execute the following command for setting the environmental variable
Depending on the type of shell, how to set the environmental variable differs.
#
Environment
Value
variable name
1
PDDIR
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
PDCONFPATH
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/conf
LD_LIBRARY_PATH
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib
PATH
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin
89
kind
of
shell
1
bash
source <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pduxenv
sh
PDDIR=<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
PDCONFPATH=<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/conf
LD_LIBRARY_PATH=<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib
PATH=<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin:$PATH
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
export PATH
csh
or
setenv
tcsh
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/conf
PDCONFPATH
setenv
LD_LIBRARY_PATH
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib
setenv
PATH
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin:${PATH}
4
Shell
other
than
the
above
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
#
Command
Display result
PDDIR=<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
(4.6.1.3)
#
1
Command
pdinfoget -m
(4.6.1.4)
[i] indicates the total sum of the values for the init_directory and
detail_directory.
90
Output example
KFPN10400-I Pdinfoget started
init_directory
= 41 Mbyte
(4.6.2)
Make sure to only execute this item in Windows. For the logs displayed in the Event Viewer, [j]
indicates the total sum of the Application and System sizes. To confirm log sizes of the event
log, see (4.5.2-1). However, when calculating make sure to use the log sizes indicated in the
Property dialog box, and not the sizes of the logs saved in text format.
(4.7) Estimating [C]: the HiCommand_log.db.jar size before compression
The size is estimated by using the total capacity of the databases that are used by Tuning
Manager.
Calculation formula
[C] = (Total capacity of the databases that are used by Tuning Manager)
(4.7.1)
Confirming the total capacity of the databases that are used by Tuning Manager
(4.7.1.1)
(4.7.1.2)
(4.7.1.3)
The total value indicated in the command execution result represents the total
(4.8.1)
The value for "Used" in (4.7.1.3) indicates Tuning Manager database usage.
[In Ver.7.0 or later, or Ver.6.4 (do not collect Agent Store DB)]
Execution results of the jpcprras command: specified-directory/PR/
Execution results of the htm-dump command: specified-directory/MC/
Execution results of the jpcras command: specified-directory/CLMgr/all
Execution results of the jpcras command: specified-directory/CLMgr/all_dump
Execution results of the jpcras command: specified-directory/CLMgr/mgr_data
If you execute the command with -z option, following file is created which contains and compressed
above files.
Execution results of htm-getlogs command with -z option: specified-directory/htm_getlogs.zip
The log files collected by the htm-getlogs command contain Agent Store Database if Agent is installed on
a same host. In the case where the size of Store database is large, following problems might occur. When
the problems occur, see 4.5 The problems in acquiring RAS information and the contingency plan.
- A long time is needed to collect RAS information.
The RAS information cannot be sent or it takes long time to send the RAS information.
When Tuning Manager server 7.0.0-00 or later is used, if HTnM server and HTnM Agents are
92
installed on a same host, please execute jpcras command after executing htm-getlogs command.
(2) Prerequisites
- To execute this command, you must have logged on as a member of the Administrators
group, root, or the equivalent.
- This command must be executed on a machine where Tuning Manager server is
installed.
- You do not need to stop the Tuning Manager server services.
- To acquire the database information about Tuning Manager Agent, the Agent services
must be stopped.
(3) Use
For details about how to use this command, see the manual.
For a list of log files acquired using this command, see Exhibit 1 Maintenance information.
Example:
In Windows:
Suite-installation-directory\TuningManager\bin\htm-getlogs -d C:\Logs -z
In Solaris:
# /opt/HiCommand/TuningManager/bin/htm-getlogs -d /export/Logs -z
In Linux:
# <TuningManager-Installation-directory> /bin/htm-getlogs -d /export/Logs -z
(2) Prerequisites
- To execute this command, you must have logged on as a member of the Administrators
group, root, or the equivalent.
- This command must be executed on a machine where Tuning Manager server is
installed.
- You do not need to stop the Tuning Manager server services.
93
- To acquire the database information about Tuning Manager Agent, the Agent services
must be stopped.
(3) Use
For details about how to use this command, see the manual.
For a list of log files acquired using this command, see Exhibit 1 Maintenance information.
Example:
In Windows:
Suite-installation-directory\TuningManager\bin\htm-dump -d C:\Logs -z
In Solaris:
# /opt/HiCommand/TuningManager /bin/htm-dump -d /export/Logs -z
In Linux:
# <TuningManager-Installation-directory> /bin/htm-dump -d /export/Logs -z
Example:
In Windows:
Suite-installation-directory\TuningManager\PerformanceReporter\tools\jpcprras C:\Logs
In Solaris:
# /opt/HiCommand/TuningManager/PerformanceReporter/tools/jpcprras /export/Logs
In Linux:
# <TuningManager-Installation-directory>/PerformanceReporter/tools/jpcprras /export/Logs
94
Note:
The log output folder (directory) specified in the jpcrpras command must be created beforehand. If
the specified folder (directory) does not exist, the command results in an error.
Service key
Product
mgr
Collection Manager
agtd
RAID Agent
agte
agtm
EAP Agent
agtn
NAS Agent
agto
Oracle Agent
agtq
SQL Agent
95
agtr
DB2 Agent
agtt
Platform Agent(Windows)
10
agtu
Platform Agent(Unix)
11
agtw
Switch Agent
12
agtz
Exchange Agent
13
act
Action Handler
14
stat
Status Server
15
agt0
Example 1: When acquiring the log and database information about Collection Manager and all
Agents running on the host where the jpcras command is executed
In Windows:
cd Suite-installation-directory\TuningManager\jp1pc\tools\
jpcras C:\Logs all all
In Unix (Linux, Solaris):
# cd /opt/jp1pc/tools
# jpcras /export/Logs all all
Example 2: When acquiring the log and database information about RAID Agent from Agent
running on the host where the jpcras command is executed
In Windows:
cd Suite-installation-directory\TuningManager\jp1pc\tools
jpcras C:\Logs agtd all
In Unix (Linux, Solaris, HP-UX, or AIX):
# cd /opt/jp1pc/tools
# jpcras /export/Logs agtd all
Example 3: When acquiring the log and database information about RAID Agent whose instance
name is LightningA from Agent running on the host where the jpcras command is executed
In Windows:
cd Suite-installation-directory\TuningManager\jp1pc\tools
jpcras C:\Logs agtd all inst=LightningA
In Unix (Linux, Solaris, HP-UX, or AIX):
# cd /opt/jp1pc/tools
# jpcras /export/Logs agtd all inst=LightningA
4.2.
In this chapter, the RAS information that cannot be the collected by the command, or the RAS
information that failed to be collected by the command, thus, expected to be manually collected, is
described.
96
Note:
If the installation log for Collection Manager (pfm_inst.log) is not found in the folder specified by
the environment variable %TEMP%, an attempt to install the software or collect logs might be
performed on a remote desktop connection when a remote session is held. In this case, use the
GUI to select [System Properties], the [Advance] tab, and then [Environment Variables]. After you
select [Environment Variables], check the value of the environment variable %TEMP% to
determine whether the log output is directed to the folder specified by the variable %TEMP% or a
subfolder of that folder. The following is an example of an output destination:
If you install the software in a remote desktop connection environment for a remote session, the
installation log output is directed to an automatically generated folder. Because this folder is
deleted when you log off, if you want to collect the installation log data, you must collect it before
97
[For Agent]
Refer to the section, Collecting information if an installation failure occurs of the following
manual:
- In Ver.6
Hitachi Tuning Manager Software Installation Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Installation Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Installation Guide
If the jpcras command cannot be used, please get following log files manually.
Table 4.2.2-1:The list of log files manually collected when the jpcras command cannot be used
#
Log Location
OS
Installed PP
Suite-installation-directory\TuningManager
Windows
Tuning
directories under
\jp1pc
Manager
server,
Log Location
Agents
/opt/jp1pc
UNIX
Tuning
Manager
server,
Agents
Eventlog
Windows
Tuning
(application),
server,
Eventlog(system)
Agents
Syslog
Default Location:
UNIX
- Case HP-UX
Tuning
Manager
Manager
server,
/var/adm/syslog/syslog.log
Agents
- Case Solaris
98
/var/adm/messages*
- Case AIX
/var/adm/syslog*
- Case Linux
/var/log/messages*
All
Agents
99
- In Windows:
<Tuning Manager server Installation
folder>\agtw\agent\instance-name\javacoreprocessID.YYMMDDhhmmss.txt
<Tuning Manager server Installation folder>\agtw\agent\instance-name\hs_err_pidprocessID.log
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/ hs_err_pidprocessID.log
Table 4.2.3-1: The list for the IF of Switch Agent and JavaVM relationship(7.0 or earlier)
Monitoring target
Version of Switch
OS
IF
Agent
Brocade
McDATA
CISCO
JavaVM is
used?
6.0 or later *1
Windows
SMI-S
Yes
6.1 or later *2
Solaris
SMI-S
Yes
6.2 or later
Windows
SMI-S
Yes
6.2 or later
Solaris
SMI-S
Yes
6.0 or later *3
Windows
SMI-S
Yes
6.1 or later *4
Solaris
SMI-S
Yes
(*1) Switch Agent changes the IF from Fabric Access API to SMI-S in version 5.9,
however, its change is only for Windows, still uses domestic API in UNIX.
(*2) Switch Agent for Solaris changed the Fabric Access API to SMI-S in version 6.1
(*3) Switch Agent for Windows started to support CISCO switches from version 5.7.
(*4) Switch Agent for Solaris started to support CISCO switches from version 6.1.
100
Table 4.2.3-2: The list for the IF of Switch Agent and JavaVM relationship (7.1 or later)
Monitoring target
Version of Switch
OS
IF
Agent
JavaVM is
used?
Brocade(DCFM
7.1 or later
Windows
SMI-S
Yes
SMI Agent)
7.1 or later
Solaris
SMI-S
Yes
7.1 or later
Linux
SMI-S
Yes
7.1 or later
Windows
SMI-S
Yes
FOS)
7.1 or later
Solaris
SMI-S
Yes
7.1 or later
Linux
SMI-S
Yes
7.1 or later
Windows
SMI-S
Yes
EOS)
7.1 or later
Solaris
SMI-S
Yes
7.1 or later
Linux
SMI-S
Yes
7.1 or later
Windows
SMI-S
Yes
7.1 or later
Solaris
SMI-S
Yes
7.1 or later
Linux
SMI-S
Yes
7.2.1 or later
Windows
SMI-S
Yes
7.2.1 or later
Solaris
SMI-S
Yes
7.2.1 or later
Linux
SMI-S
Yes
CISCO(Seed Switch)
CISCO(DCNM-SAN SMI-S
Agent)
(2) When network communication issue occurs for monitoring Brocade switches(B-Model),
Brocade switches(M-Model), or Cisco switches.
If you face with the issue related with network communication, please get the network traffic
information to identify the cause by the following procedure.
101
(B) Please collect detailed XML trace log and DCFM SMI Agent log data by the following
procedure.
How_to_collect_deta
iled_XML_TraceLog(D
(3.2) For Brocade(7.0 or earlier) or Brocade(SMI Agent for FOS) (7.1 or later)
Log in to the switch specified as Proxy Switch via telnet, and get the log file by using the
following command. Note that the supportSave command is available from firmware version
4.4.0c or later, and it internally calls the supportShow command and also gets the trace log etc
of Brocade switch (B-Model).
Table 4.2.3-3 The list of the command used for getting log files of Brocade switches
Firmware version of
SupportShow
V4.4.0c or later
SupportSave
<When Switch Agent version 6.0 or later is used in Windows or version 6.1 to earlier than 8.0
is used in Soalris or version 7.1 or later is used in Linux>
If Switch Agent version 5.9 or later is used in Windows OS or version 6.1 or later is used in
Soalris or version 7.1 or later is used in Linux, it actually uses SMI-S to get the data from
Brocade switch (B-Model) instead of using Fabric Access API. In this case, get the following
log files.
(A) All log files got by [Agent Support Show] of [Brocade SMI Agent Configuration Tool]
of SMI Agent.
(B) Please collect detailed XML trace log and SMI Agent log data by the following
procedure.
How_to_collect_deta
iled_XML_TraceLog(F
102
Collecting XML trace and DCFM SMI Agent logs when using
DCFM SMI Agent to monitor Brocade switches
1.
Overview
If an error occurs in an instance of HTnM - Agent for SAN Switch (Agent for SAN
Switch hereafter) that monitors a Brocade switch, you must collect the DCFM SMI
Agent supportsave data.
In addition to the DCFM SMI Agent supportsave data, you must also collect XML
trace log data that contains all output data including data about communication
between Agent for SAN Switch and DCFM SMI Agent.
The XML trace log data is output at the following two levels:
Level
Level 1
Information output
Timestamps only
Usage
Investigation of ordinary
failures
Level 2
Investigation of failures
communication data
The default setting is Level 1. For this level, only timestamps are output.
If a problem occurs, set the log output level to Level 2 to collect all data, including
communication data (referred to hereafter as detailed XML trace log data).
This document describes how to collect supportsave data as well as detailed XML
trace log data.
2.
Prerequisites
3.
Notes
When you collect DCFM SMI Agent supportsave data, and detailed XML trace log
1Given 4096 KB (file size) x 64 (number of files) = 256 MB, the actual file size might be as
much as 1 MB larger than the specified size, depending on the output format of the XML
data. Therefore, the file size might reach 5 MB x 64 (number of files) = 320 MB.
- In Solaris, Linux:
Start the console.
(2) Stopping the instance
Stop the instance by executing the following command:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstop agtw inst=instance-name
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstop agtw inst=instance-name
After successfully completing execution of the jpcstop command, execute the
following command to make sure that the instance has stopped (the status is
Inactive).
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
- In Solaris, Linux:
Start DCFM server by executing the following command from the console:
cd DCFM-installation-directory/bin
./dcfm
(3) In the DCFM menu, click Monitor, Technical Support, and then Switch / Host SupportSave.
(4) In the Technical Support Save window, click the Generate Now tab.
(5) In the Generate Now tab, click the Switches tab.
(6) Select a switch from Available Switches, and click the right arrow button to move the switch to
Selected Switches and Hosts.
(7) In the Generate Now window, click the Hosts tab.
(8) In the same way as step (4), select a host from Available Hosts and click the right arrow button
to move the switch to Selected Switches and Hosts.
(9) Click the OK button at the bottom of the Technical SupportSave window.
If the version of Fabric OS running on a selected switch is 5.1 or earlier, the following error message
is displayed and no log files can be collected for the switch. To collect log files for the switch,
execute the SupportSave command.
(2) DCFM Server Console is opened, and then choose Technical Support Information
tab.
(3) Set an output path to Output Path for collecting materials.
4.4. Specifying output settings for detailed XML trace log data
(1) Opening the jpcagt.ini file
- In Windows:
Open the HTM-installation-directory\jp1pc\agtw\agent\instance-name\jpcagt.ini
file using a text editor.
- In Solaris, Linux:
Open the /opt/jp1pc/agtw/agent/instance-name/jpcagt.ini file using an editor.
10
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstart agtw inst=instance-name
11
5.
- In Solaris, Linux:
/opt/jp1pc/tools/jpcras
path-to-directory-where-maintenance-information-is-stored agtw all
(For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.)
When you execute the command, the following message appears and maintenance
information is collected:
KAVE06009-I The collection of maintenance information will now start.
Verify that the following message is output. If it is output, collection has successfully
ended.
KAVE06010-I The collection of maintenance information ended normally.
12
Figure 5.1-2 Display when maintenance information collection has successfully ended
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1
(2) Saving the settings
After you make the changes, save the settings, and then close the jpcagt.ini file.
6.2. Deleting XML trace log data
The next step is to delete the detailed XML trace log data.
Delete the following file:
13
File to be deleted:
CIMClientXML_Trace[?].txt
(In the above, ? is a numeric value from 0 to 63.)
6.3. Restarting the Agent for SAN Switch instance
Perform the procedure described in 4.1 Stopping the Agent for SAN Switch instance to
start Command Prompt. Execute the jpcstart command to restart the instance.
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstart agtw inst=instance-name
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstart agtw inst=instance-name
-End of document-
14
Collecting XML trace and SMI Agent for FOS logs when using
SMI Agent for FOS to monitor Brocade switches (B-Model)
1.
Overview
If an error occurs in an HTnM - Agent for SAN Switch (hereafter Agent for SAN Switch) instance
that uses SMI Agent for FOS to monitor Brocade switches (B-Model), you must collect the SMI
Agent for FOS CIMOM log data, Provider log data, and all other data including communication
data.
XML trace log data is output when Agent for SAN Switch is used to monitor Brocade
Switches (B-Model).
The XML trace log data is output at the following two levels:
Level
Level 1
Information output
Timestamps only
Usage
Investigation of ordinary
failures
Level 2
Investigation of FC
communication data
The default setting is Level 1. For this level, only timestamps are output.
If a failure occurs while Brocade Switches (B-Model) are being monitored, and the
failure seems to have been caused by an FC switch (for example, there are no
communication problems but the data is not correct), set the log output level to Level
2 to collect all data, including communication data (referred to hereafter as detailed
2.
Prerequisites
3.
Notes
When you collect SMI Agent for FOS CIMOM log data, provider log data and detailed
XML trace log data, note the following:
(1) When you collect the CIMOM log data, provider log data and detailed XML trace log
data, you must specify the configuration beforehand according to the procedures
described in 4. Preconfiguration for Collecting CIMOM log Data and Provider log
Data.
(2) To collect the CIMOM log data, provider log data and detailed XML trace log data,
you must temporarily stop the Agent for SAN Switch instance.
(3) When you collect the CIMOM log data and provider log data, make sure that there is
enough space on the drive where SMI Agent for FOS is installed. SMI Agent for FOS
data requires a lot of disk space.
(4) When you collect detailed XML trace log data, make sure that there is enough disk
space on the drive on which HTM is installed, because the amount of detailed XML
trace log data is very large.
When you collect detailed XML trace log data, you specify a file size and the number
of files. However, the size for one line of detailed XML trace log data is large, so the
specified file size might be exceeded. Accordingly, the procedure described in this
document requires about 320 MB 1 of free disk space.
(5) Since the CPU usage rate increases when you collect CIMOM log data and provider
log data, SMI Agent for FOS performance might be significantly degraded.
Therefore, when the data on SMI Agent for FOS has been collected, restore the
original configuration by performing the procedure described in 6. Procedure for
Therefore, after detailed XML trace log data is collected, restore the original settings
as described in 6. Procedure for Restoring the Environment.
4.
Preconfiguration for Collecting CIMOM log Data and Provider log Data
To collect CIMOM log data and provider log data, you must change the configuration
by using Brocade SMI Agent Configuration Tool.
To output detailed XML trace log data, you must manually change the value set for
certain properties defined in the following file:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
- In Solaris, Linux:
Start the console.
(2) Stopping an instance
Stop the appropriate instance by executing the following command:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstop agtw inst=instance-name
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstop agtw inst=instance-name
After successfully completing execution of the jpcstop command, execute the
following command to make sure that the instance has stopped (the status is
Inactive).
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
When SMI Agent for FOS is used to monitor Brocade switches (B-Model), either of the
following messages may be displayed and a timeout may occur depending on the size
of the instance that is being monitored. If a timeout occurs, wait a while before
executing the above command to make sure that the instance has stopped (the status
is Inactive).
KAVE05034-E A service could not stop. (service=Agent for SANSwitch,
inst=instance-name, rc=-13)
KAVE05237-E The service did not return the response to the request of the jpcstop
command in time.(service=Agent for SANSwitch, inst=instance-name, rc=-2)
version, and then Brocade SMI Agent Configuration Tool to start Brocade SMI
Agent Configuration Tool (The following figure shows a Windows 2000 Advanced
Server screenshot).
Figure 4.2-1 Starting Brocade SMI Agent Configuration Tool when SMI Agent for FOS 120.6.0a is
used
- In Solaris, Linux:
Start Brocade SMI Agent Configuration Tool by executing the following command:
SMI-Agent-for-FOS-installation-directory/agent/server/jserver/bin/configurationtool.sh
Menu tree
Action buttons
Server buttons
Figure 4.2-2 Brocade SMI Agent Configuration Tool Screenshot and Description of Sections
Figure 4.3-1 Window for Configuring CIMOM log of SMI Agent for FOS 120.6.0a (Before
Configuration)
(a)
(b)
(d)
(c)
(e)
(f)
(g)
Figure 4.3-2 Window for Configuring CIMOM log of SMI Agent for FOS 120.6.0a (After
Configuration)
4.3.2.
Configuring CIMOM log by using SMI Agent for FOS 120.7.1, 120.7.2,
120.8.0, 120.9.0 and 120.11.0
Figure 4.3-3 Window for Configuring CIMOM log of SMI Agent for FOS 120.7.1 (Before
Configuration)
10
Figure 4.3-4 Window for Configuring CIMOM log of SMI Agent for FOS 120.7.1 (After
Configuration)
11
12
(a)
(b)
(c)
(d)
13
Figure 4.4-3 Window for Specifying the Debug Configuration (Before Specification)
14
(a)
(b)
(c)
(d)
(f)
(e)
(g)
(h)
(i)
Figure 4.4-4 Window for Specifying the Debug Configuration (After Specification)
15
4.5. Specifying output settings for the detailed XML trace log data
(1) Open the jpcagt.ini file.
Use a text editor to open the jpcagt.ini file located in:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
16
(2) Change the values of properties related to the XML trace log.
In the Agent section, change the values of the properties related to the XML trace log
as follows:
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2
17
18
5.
Collecting the SMI Agent for FOS CIMOM Log Data and Provider Log Data
This chapter describes how to collect SMI Agent for FOS CIMOM log data and
Provider log data.
5.1. Replicating the failure
Replicate the failure.
5.2. Stopping the Agent for SAN Switch instance
When you replicate the failure, perform the procedure described in 4.1. Stopping the
Agent for SAN Switch instance to start Command Prompt. Execute the jpcstop
command to stop the instance.
5.3. Stopping SMI Agent for FOS
(1) Starting Brocade SMI Agent Configuration Tool
Perform the procedure described in 4.2. Starting Brocade SMI Agent Configuration
19
- In Solaris, Linux:
SMI-Agent-for-FOS-installation-directory/agent/server/jserver/bin
20
For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.
When you execute the command, the following message appears and maintenance
information is collected:
KAVE06009-I The collection of maintenance information will now start.
21
22
6.
When data collection by SMI Agent for FOS is complete, perform the following
procedure to restore the original configuration.
6.1. Restoring the CIMOM log configuration
6.1.1.
Restoring the CIMOM log configuration by using SMI Agent for FOS
120.6.0a
Figure 6.1-1 Window for Configuring the CIMOM log of SMI Agent for FOS 120.6.0a (Before
Configuration)
23
(a)
(b)
Figure 6.1-2 Window for Configuring the CIMOM log of SMI Agent for FOS 120.6.0a (After
Configuration)
24
6.1.2.
Restoring the CIMOM log configuration by using SMI Agent for FOS
120.7.1, 120.7.2, 120.8.0, 120.9.0 and 120.11.0
Figure 6.1-3 Window for Configuring the CIMOM log of SMI Agent for FOS 120.7.1 (Before
Configuration)
25
Figure 6.1-4 Window for Configuring the CIMOM log of SMI Agent for FOS 120.7.1 (After
Configuration)
26
27
(a)
28
29
30
(3.3) For McDATA(7.0 or earlier) or Brocade(SMI Agent for EOS) (7.1 or later)
(A)If EFCM is used for monitoring, log in to EFCM Server from EFCM Client, and then
acquire the following logs:
- Audit Log
- Event Log
- Fabric Log
- Hardware Log
- Link Incident Log
- Product Status Log
- Threshold Alert Log
(B)If DCFM is used for monitoring, log in to DCFM Server from DCFM Client, and then
acquire the following logs:
- Audit Log
- Event Log
- Fabric Log
- FICON Log
- Product Status Log
- Security Log
- Syslog Log
- Technical Support Information
(C) Please collect detailed XML trace log and SMI Agent for EOS log data by the
following procedure.
How_to_collect_deta
iled_XML_TraceLog(E
(B) please collect detailed XML trace log data by the following procedure.
How_to_collect_deta
iled_XML_TraceLog(S
103
Collecting XML trace and SMI Agent for EOS logs when using
SMI Agent for EOS to monitor Brocade switches (M-Model)
1.
Overview
If an error occurs in a HTnM - Agent for SAN Switch (hereafter Agent for SAN Switch)
instance that uses SMI Agent for EOS to monitor Brocade switches (M-Model), you must collect
the SMI Agent for EOS audit log data and the debug log data.
In addition to the SMI Agent for EOS audit log data and debug log data, you must
also collect XML trace log data that contains all output data including data about
communication between Agent for SAN Switch and SMI Agent for EOS.
The XML trace log data is output at the following two levels:
Level
Level 1
Information output
Timestamps only
Usage
Investigation of ordinary
failures
Level 2
The default setting is Level 1. For this level, only timestamps are output.
If a problem occurs, set the log output level to Level 2 to collect all data, including
communication data (referred to hereafter as detailed XML trace log data).
This document describes how to collect audit log data and debug log data as well as
detailed XML trace log data.
2.
Prerequisites
3.
Notes
When you collect SMI Agent for EOS audit log data, debug log data, and detailed
Required for Collecting Debug Log Data and Detailed XML Trace Log Data.
(2) You do not need to change the SMI Agent for EOS configuration when collecting
audit log data because SMI Agent for EOS collects audit log data by default.
(3) To collect audit log data, debug log data, and detailed XML trace log data, you must
temporarily stop the Agent for SAN Switch instance.
(4) When you collect debug log data, make sure that there is at least 40 MB of free space
on the drive where SMI Agent for EOS is installed.
(5) When you collect detailed XML trace log data, make sure that there is enough free
space on the drive where HTnM is installed, because the amount of detailed XML
trace log data is very large.
When you collect detailed XML trace log data, you specify a file size and the number
of files. However, one line of detailed XML trace log data also contains such a large
amount of data that the file with the specified file size might overflow. Accordingly,
the procedure described here requires about 320 MB 1 of free disk space.
(6) Since the CPU usage rate increases when you collect debug log data, the SMI Agent
for EOS performance might be significantly degraded.
Therefore, when debug log data has been collected, restore the original configuration
by performing the procedure described in 6. Procedure for Restoring the Environment.
(7) Since the CPU usage rate increases when you collect detailed XML trace log data,
the Agent for SAN Switch performance might be significantly degraded.
Therefore, when detailed XML trace log data has been collected, restore the original
configuration by performing the procedure described in 6. Procedure for Restoring the
Environment.
4.
Preconfiguration Required for Collecting Debug Log Data and Detailed XML
Trace Log Data
To collect debug log data, you must change the configuration by using Server
Configuration Tool provided by SMI Agent for EOS.
To output detailed XML trace log data, you must manually change the values set for
certain properties defined in the following file:
1Given 4096 KB (file size) x 64 (number of files) = 256 MB, the actual file size might be as
much as 1 MB larger than the specified size, depending on the output format of the XML
data. Therefore, the file size might reach 5 MB x 64 (number of files) = 320 MB.
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
- In Solaris, Linux:
Start the console.
(2) Stopping the instance
Stop the instance by executing the following command:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstop agtw inst=instance-name
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstop agtw inst=instance-name
After successfully completing execution of the jpcstop command, execute the
following command to make sure that the instance has stopped (the status is
Inactive).
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
- In Solaris, Linux:
Start Server Configuration Tool by executing the following command from the
console:
SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin/McDATA_server_c
onfiguration_tool.sh
Figure 4.3-1 Window for debug log configuration (before configuration change)
Figure 4.3-2 Window for debug log configuration (after configuration change)
- In Solaris, Linux:
Open the /opt/jp1pc/agtw/agent/instance-name/jpcagt.ini file using an editor.
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstart agtw inst=instance-name
5.
Collecting SMI Agent for EOS Audit Log Data, Debug Log Data, and Detailed
XML Trace Log Data
This chapter describes how to collect SMI Agent for EOS audit log data, debug log
Agent for SAN Switch instance to start Command Prompt. Execute the jpcstop
command to stop the instance.
10
5.3. Executing the tool for collecting SMI Agent for EOS log data
Using the tool for collecting SMI Agent for EOS log data, obtain the necessary log
data. Execute the following command:
- In Windows:
cd /d SMI-Agent-for-EOS-installation-directory\agent\server\jserver\bin
statusexporter.bat
- In Solaris, Linux:
cd SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin
statusexporter.sh
After verifying that the message is displayed, obtain the file that has been created
by the tool in the following folder:
- In Windows:
Log data collection tool output folder name:
SMI-Agent-for-EOS-installation-directory\agent\server\jserver\bin
Name of file created by log data collection tool:
smisstatusexport.zip
statusexporter bat
- In Solaris, Linux:
Log data collection tool output folder name:
SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin
Name of file created by log data collection tool:
smisstatusexport.zip
statusexporter bat
11
- In Solaris, Linux:
/opt/jp1pc/tools/jpcras
path-to-directory-where-maintenance-information-is-stored agtw all
(For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.)
When you execute the command, the following message appears and maintenance
information is collected:
KAVE06009-I The collection of maintenance information will now start.
Verify that the following message is output. If it is output, collection has successfully
ended.
KAVE06010-I The collection of maintenance information ended normally.
12
Figure 5.4-2 Display when maintenance information collection has successfully ended
6.
13
Figure 6.1-1 Window for debug log configuration (before configuration restoration)
14
Figure 6.1-2 Window for debug log configuration (after configuration restoration)
15
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1
File to be deleted:
CIMClientXML_Trace[?].txt
(In the above, [?]is a numeric value from 0 to 63.)
6.4. Restarting SMI Agent for EOS
Perform the procedure described in 4.6. Stopping and restarting SMI Agent for EOS
to restart SMI Agent for EOS.
6.5. Restarting the Agent for SAN Switch instance
Perform the procedure described in 4.1. Stopping the Agent for SAN Switch instance
to start Command Prompt. Execute the jpcstart command to restart the instance.
16
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstart agtw inst=instance-name
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstart agtw inst=instance-name
-End of document-
17
Overview
XML trace log data is output when HTnM - Agent for SAN Switch (referred to
hereafter as Agent for SAN Switch ) is used to monitor Cisco switches.
The XML trace log data is output at the following two levels:
Level
Level 1
Information output
Timestamps only
Usage
Investigation of ordinary
failures
Level 2
Investigation of FC
communication data
The default setting is Level 1. For this level, only timestamps are output.
If a failure occurs while Cisco switches are being monitored, and the failure seems to
have been caused by an FC switch (for example, there are no communication problems
but the data is not correct), set the log output level to Level 2 to collect all data,
including communication data (referred to hereafter as detailed XML trace log data).
This document describes how to collect detailed XML trace log data.
2.
Prerequisite Product
- HTnM - Agent for SAN Switch for Windows Version 5.9.0-00 or later
- HTnM - Agent for SAN Switch for Solaris Version 6.1.0-00 to earlier than 8.0.0
- HTnM - Agent for SAN Switch for Linux Version 7.1.0-00 or later
3.
Notes
This section provides notes on collecting detailed XML trace log data.
(1) Before you can collect detailed XML trace log data, you must change the settings as
described in 4. Procedure for collecting detailed XML trace log data.
(2) To collect detailed XML trace log data, you must first stop all Agent for SAN Switch
instances.
(3) When you collect detailed XML trace log data, make sure that there is enough disk
space on the drive on which HTnM is installed, because the amount of detailed XML
trace log data is very large.
When you collect detailed XML trace log data, you specify a file size and the number
of files. However, the size for one line of detailed XML trace log data is large, so the
specified file size might be exceeded. Accordingly, the procedure described in this
document requires about 320 MB 1 of free disk space.
(4) While detailed XML trace log data is being collected, the CPU usage rate becomes
high. As a result, the performance of Agent for SAN Switch could significantly
degrade.
Therefore, after detailed XML trace log data is collected, restore the original settings
as described in 6. Restoring the environment.
4.
To output detailed XML trace log data, you must manually change the value set for
certain properties defined in the following file:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
1 Although 4096 KB (file size) x 64 (number of files) = 256 MB, the actual file size might be
as much as 1 MB larger than the specified size, depending on the output format of the XML
data. Therefore, the file size might reach 5 MB x 64 (number of files) = 320 MB.
- In Solaris, Linux:
Start the console.
(2) Stop the instance of Agent for SAN Switch.
To stop the applicable instance, execute the following command:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstop agtw inst=instance-name
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstop agtw inst=instance-name
Even if the above command terminated normally, execute the following command to
confirm that the instance stopped (the status is "Inactive"):
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
4.2. Specifying output settings for the detailed XML trace log data
(1) Open the jpcagt.ini file.
Use a text editor to open the jpcagt.ini file located in:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
(2) Change the values of properties related to the XML trace log.
In the Agent section, change the values of the properties related to the XML trace log
as follows:
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2
Switch. Next, execute the jpcstart command as follows to start the instance:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstart agtw inst=instance-name
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstart agtw inst=instance-name
When the data collection event starts after the instance has started, detailed XML
trace log data is output to the directory shown below. If a failure occurs, stop the
instance as described in 4.1. Stopping an instance of Agent for SAN Switch.
Output directory:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name
Name of output files:
CIMClientXML_Trace [?].txt
(In the above, [?] is a numeric value from 0 to 63.)
5.
This chapter describes how to collect information by executing the jpcras command.
5.1. Stopping all instances of Agent for SAN Switch
Start Command Prompt as described in 4.1. Stopping an instance of Agent for SAN
Switch. Execute the jpcstop command as follows to stop all instances of Agent for SAN
Switch:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstop agtw
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstop agtw
Even if the above command terminated normally, execute the following command to
confirm that the instances stopped (the status is "Inactive"):
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.
When you execute the command, the following message appears and maintenance
information is collected:
KAVE06009-I The collection of maintenance information will now start.
10
11
6.
After the collection of detailed XML trace log data finishes, perform the following
procedure to restore the original settings.
6.1. Stopping an instance of Agent for SAN Switch
If the instance of Agent for SAN Switch has not stopped, stop it as described in 4.1.
12
13
(B) please collect detailed XML trace log data and DCNM-SAN support information by
the following procedure.
How_to_collect_deta
iled_XML_TraceLog(S
4.2.5 htm-csv-convert
If the htm-csv-convert command fails to convert the input file, you need to manually collect the
input file specified in the command.
4.3.
In this chapter, the approximate required time for the execution of the each RAS command is
described. Please use this information to estimate the required time for getting RAS information.
Also, refer the Table 4.1-1 to select what RAS command should be executed.
Table 4.3-1: The server environment used for RAS command measurement
Server A
Server B
6.0.0
Device Manager version 6.0.0
104
Overview
XML trace log data is output when HTnM - Agent for SAN Switch (referred to
hereafter as Agent for SAN Switch ) is used to monitor Cisco switches.
The XML trace log data is output at the following two levels:
Level
Level 1
Information output
Timestamps only
Usage
Investigation of ordinary
failures
Level 2
Investigation of FC
communication data
The default setting is Level 1. For this level, only timestamps are output.
If a failure occurs while Cisco switches are being monitored, and the failure seems to
have been caused by an FC switch (for example, there are no communication problems
but the data is not correct), set the log output level to Level 2 to collect all data,
including communication data (referred to hereafter as detailed XML trace log data).
This document describes how to collect detailed XML trace log data.
2.
Prerequisite Product
- HTnM - Agent for SAN Switch for Windows Version 7.2.1-00 or later
- HTnM - Agent for SAN Switch for Solaris Version 7.2.1-00 to earlier than 8.0.0
- HTnM - Agent for SAN Switch for Linux Version 7.2.1-00 or later
3.
Notes
This section provides notes on collecting detailed XML trace log data.
(1) Before you can collect detailed XML trace log data, you must change the settings as
described in 4. Procedure for collecting detailed XML trace log data.
(2) To collect detailed XML trace log data, you must first stop all Agent for SAN Switch
instances.
(3) When you collect detailed XML trace log data, make sure that there is enough disk
space on the drive on which HTnM is installed, because the amount of detailed XML
trace log data is very large.
When you collect detailed XML trace log data, you specify a file size and the number
of files. However, the size for one line of detailed XML trace log data is large, so the
specified file size might be exceeded. Accordingly, the procedure described in this
document requires about 320 MB 1 of free disk space.
(4) While detailed XML trace log data is being collected, the CPU usage rate becomes
high. As a result, the performance of Agent for SAN Switch could significantly
degrade.
Therefore, after detailed XML trace log data is collected, restore the original settings
as described in 6. Restoring the environment.
4.
To output detailed XML trace log data, you must manually change the value set for
certain properties defined in the following file:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
1 Although 4096 KB (file size) x 64 (number of files) = 256 MB, the actual file size might be
as much as 1 MB larger than the specified size, depending on the output format of the XML
data. Therefore, the file size might reach 5 MB x 64 (number of files) = 320 MB.
- In Solaris, Linux:
Start the console.
(2) Stop the instance of Agent for SAN Switch.
To stop the applicable instance, execute the following command:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstop agtw inst=instance-name
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstop agtw inst=instance-name
Even if the above command terminated normally, execute the following command to
confirm that the instance stopped (the status is "Inactive"):
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
4.3. Specifying output settings for the detailed XML trace log data
(1) Open the jpcagt.ini file.
Use a text editor to open the jpcagt.ini file located in:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
(2) Change the values of properties related to the XML trace log.
In the Agent section, change the values of the properties related to the XML trace log
as follows:
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2
Switch. Next, execute the jpcstart command as follows to start the instance:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstart agtw inst=instance-name
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstart agtw inst=instance-name
When the data collection event starts after the instance has started, detailed XML
trace log data is output to the directory shown below. If a failure occurs, stop the
instance as described in 4.1. Stopping an instance of Agent for SAN Switch.
Output directory:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name
Name of output files:
CIMClientXML_Trace [?].txt
(In the above, [?] is a numeric value from 0 to 63.)
10
5.
This chapter describes how to collect information by executing the jpcras command.
5.1. Stopping all instances of Agent for SAN Switch
Start Command Prompt as described in 4.1. Stopping an instance of Agent for SAN
Switch. Execute the jpcstop command as follows to stop all instances of Agent for SAN
Switch:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstop agtw
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstop agtw
Even if the above command terminated normally, execute the following command to
confirm that the instances stopped (the status is "Inactive"):
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
11
For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.
When you execute the command, the following message appears and maintenance
information is collected:
KAVE06009-I The collection of maintenance information will now start.
12
13
6.
After the collection of detailed XML trace log data finishes, perform the following
procedure to restore the original settings.
6.1. Stopping an instance of Agent for SAN Switch
If the instance of Agent for SAN Switch has not stopped, stop it as described in 4.1.
14
15
OS
CPU
Memory
4 GB
4 GB
Table 4.3-2: The monitored storage used for RAS command measurement
Monitored Storage
Resource Type
Number of Resources
Hitachi Universal
Storage Platform V
Logical device
61,739
LUSE
1,270
VDEV
57,355
Array group
96
Port
96
CLPR
Pool
12
Table 4.3-3: The result of the required time for getting RAS information
Command
hcmdsgetlogs
952
htm-getlogs
243
htm-dump
14
jpcprras
66
jpcras (Server A)
24
jpcras (Server B)
30
4.4.1 The number and size of Main Console trace log files
To change the number or size of Main Console trace log files (htmTrace.log), add properties and
values to the system.logging.properties private properties file.
The system.logging.properties file is stored in the following location.
In Windows:
<Hitachi-Tuning-Manager-installation-folder>\system\sysconf\system.logging.properties
In Solaris:
/opt/HiCommand/TuningManager/system/sysconf/system.logging.properties
105
In Linux:
<Hitachi-Tuning-Manager-installation-directory>/system/sysconf/system.logging.properties
Description
trace.fileN
The maximum allowable number of Main Console trace log files. Specify an
um
trace.fileS
The file size of Main Console trace logs (in MB). Specify an integer from 1 to
ize
Note: When the size of the current log file exceeds the specified value, a new file is created with a
log file number one greater than the current file name. When the number of log files exceeds
the maximum limit, the oldest file is overwritten with new data in a round robin manner.
To change the settings in the system.logging.properties file:
1) Stop the HiCommand Suite Tuning Manager service.
[ In Ver.6 to earlier than 8 ]
In Windows:
<Common-Component-installation-folder>\bin\hcmdssrv /stop /server TuningManager
In Solaris:
/opt/HiCommand/Base/bin/hcmdssrv -stop -server TuningManager
In Linux:
<Common-Component-Installation-directory>/bin/hcmdssrv -stop -server TuningManager
[ In Ver.8 or later ]
In Windows:
<Common-Component-installation-folder>\bin\hcmds64srv /stop /server TuningManager
In Linux:
<Common-Component-Installation-directory>/bin/hcmds64srv -stop -server TuningManager
2) Open the system.logging.properties file in a text editor, add properties in the
following format, and then save the file. For details about the values to be specified, see
Table 4.4-1.
<key>=<value>
Note:
A line starting with a hash mark (#) is handled as a comment line.
[ In Ver.8 or later ]
In Windows:
<Common-Component-installation-folder>\bin\hcmds64srv /start /server TuningManager
In Linux:
<Common-Component-Installation-directory>/bin/hcmds64srv -start -server TuningManager
4.4.2 Number, size, and output level of Hybrid Store trace log files
To change the number, size, and output level of Hybrid Store trace log files
(htmRestDbEngineTrace.log), add properties and values to the
sdblogger.properties private properties file.
The sdblogger.properties file is stored in the following location.
In Windows:
<Agent-Installation-folder>\htnm\agent\system\sdblogger.properties
In Linux:
<Agent-Installation-directory>/htnm/agent/system/sdblogger.properties
Description
db.log.trace.file
.number
db.log.trace.file.
The file size of Hybrid Store trace logs (in MB). Specify an integer
size
db.log.trace.outpu
The output level of Hybrid Store trace logs. The user can specify 10,
t.level
20, or 30. The greater the value, the more detailed logs can be output.
The default value is 20.
107
Note: When the size of the current log file exceeds the specified value, a new file is created with a
log file number one greater than the current file name. When the number of log files exceeds
the maximum limit, the oldest file is overwritten with new data in a round robin manner.
Note: The properties file contains properties not listed in Table 4.4-2, but the values and
names of these properties must not be changed.
To change the settings in the sdblogger.properties file:
1) Stop the service of the Tuning Manager Agent REST API component.
In Windows:
<Agent-Installation-folder>\htnm\bin\htmsrv stop -webservice
In Linux:
<Agent-Installation-directory>/htnm/bin/htmsrv stop -webservice
2) Open the sdblogger.properties file in a text editor, add properties in the format
below, and then save the file. For details about the values to be specified, see Table 4.4-2.
<key>=<value>
Note:
A line starting with a hash mark (#) is handled as a comment line.
3) Restart the service of the Tuning Manager Agent REST API component.
In Windows:
<Agent-Installation-folder>\htnm\bin\htmsrv start -webservice
In Linux:
<Agent-Installation-directory>/htnm/bin/htmsrv start -webservice
4.5 The problems in acquiring RAS information and the contingency plan. (Only in
Ver.6.4)
The problems and their solutions described in this section only apply to version 6.4. They do not
apply to version 7.0 or later, or to version 6.3 or earlier.
a same host, following problems might occur because the size of RAS information to be
collected become large due to the large Agent store database .
-
The RAS information cannot be sent to Software division or it takes long time to send the RAS
information.
STEP1-1
Collect the RAS information except Agent Store database by the hcmdsgetlogs
command or htm-getlogs command, and send the RAS information collected by STEP1-1
while executing STEP1-2 because it might take long time to complete STEP1-2.
STEP1-2
Collect the Agent Store database by the jpcras command with the option all all.
The performance data that was stored into Agent Store database at the time of
trouble occurrence might be deleted by retention period. Therefore the STEP1-2 that
collect Agent Store database is indispensable and HDS has to keep the result.
STEP 2
If Software division require the result of the STEP1-2, send the result to Software division.
Customer
STEP1-1
Send the result of the
HDS
Software
GSC
Division
log analysis.
RAS Info. by
the jpcras
command
STEP1-2
STEP2
in HDS
if Software division
require the result.
109
4.5.3 Prerequisites
(1) The version of Tuning Manager server is 6.4.0
(2) Tuning Manager server and Agent are installed on a same host(see Table 4.5-2)
Notice:If Tuning Manager server is not version 6.4.0, the contingency plan cannot be applied.
110
Table 4.5-2: Relationships between installed software and commands for collecting RAS
info.
Conventional way
Server only
Agent
hcmdsgetlogs
jpcras
with
hcmdsgetlogs
(same as above)
(same as above)
hcmdsgetlogs*
+
jpcraswith option all all
* Execute the hcmdsgetlogs command with the setting excluding Agent Store Database
that is explained bellow.
Execute STEP1-1, STEP1-2 and STEP2 explained as follows.
- STEP1
(STEP1-1)
Define the following environment variable(secret function) and execute the hcmdsgetlogs
command or htm-getlogs command. For the other usage of this command, see the manual.
#
1
Value to set
1
The behavior of the hcmdsgetlogs command and htm-getlogs command are changed
as
explained
Table
4.5-2
by
defining
the
environment
variable
HTM_NOCOLLECT_AGTSTORE.
111
Is
environment database
variable
excluded in
RAS Info?
specified-directory*/ClMgr/all
(1)Log info.
(2)OS info.
(3)Product info.
(4)Database info. on
(a)Alarm definition info.
(b)Alarm event info.
specified-directory*/ClMgr/all_dump
(5)Dump info.
specified-directory*/ClMgr/mgr_data
(4)Database info. on
(a)Alarm definition info.
(b)Alarm event info.
(c)User/report definition.
(otherwise)
specified-directory*/ClMgr/
(1)Log info.
(2)OS info.
(3)Product info.
(4)Database info. on
(a)Alarm definition info.
(b)Alarm event info.
(c)User/report definition
(d)Agent Store Database
(5)Dump info.
Legend:
Y: Agent Store Database is excluded in RAS info to be collected.
N: Agent Store Database is included in RAS info to be collected.
* In the case of the hcmdsgetlogs command, specified-directory is the directory
TuningManager included in HiCommand_log.jar created by the hcmdsgetlogs
command. In the case of the htm-getlogs command, specified-directory is the
directory specified at the command.
Examples:When Tuning Manager server and Agent are installed in a host
In Windows:
set HTM_NOCOLLECT_AGTSTORE=1
Suite-installation-directory\Base\bin\hcmdsgetlogs /dir C:\Log
112
STEP2
If Software division require the result of the STEP2, send the result to Software division.
113
4.6. Collecting data when a problem occurs while displaying a chart in Adobe Flash
Player (Tuning Manager server v7.3.0 and later)
In Tuning Manager server v7.3.0 and later, some of the charts that are displayed in the Main
Console can also be displayed in Adobe Flash Player (hereinafter "Flash"). However, if a chart fails
to display correctly in Flash, you might need to dump the chart information (XML) to analyze the
error. The error investigation data that is collected by using the hcmdsgetlogs command, which
is described in 4.1.1, contains the log data of Tuning Manager server. This log data contains
information about client access to Tuning Manager server (information about the OS, Web browser,
and Flash version). To analyze the cause of the error, this information is used to investigate the log
data and reconstruct (through the use of software) the environment in which the error occurred.
However, if you are unable to determine the cause of the error, you might be required to dump the
information in the chart viewed by the customer in order to conduct a more detailed investigation.
The following explains how to dump the chart information:
(1)
For Solaris:
/opt/HiCommand/Base/bin/hcmdssrv -stop -server TuningManager
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmdssrv stop
-server TuningManager
[ In Ver.8.0.0 or later ]
For Windows:
<Hitachi-Command-Suite-CommonComponent-installation-folder>\bin\hcmds64srv /stop
/server TuningManager
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmds64srv stop
-server TuningManager
For Solaris:
/opt/HiCommand/TuningManager/conf/user.properties
114
For Linux:
<Tuning-Manager-server-installation-directory>/conf/user.properties
Use a text editor to open the user property file and add the dumpChartXML property as follows:
dumpChartXML=true
For Solaris:
/opt/HiCommand/Base/bin/hcmdssrv -start -server TuningManager
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmdssrv start
-server TuningManager
[ In Ver.8.0.0 or later ]
For Windows:
<Hitachi-Command-Suite-Common-Component-installation-folder>\bin\hcmds64srv /start
/server TuningManager
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmds64srv start
-server TuningManager
(4) Log in to the Main Console and display the chart in which the problem occurred.
Log in to Main Console and display the chart that failed to display correctly. The dump file that
contains the chart information is output when you display the chart.
For Solaris:
/opt/HiCommand/TuningManager/logs
For Linux:
<Tuning-Manager-server-installation-directory>/logs
(9) Delete the dump file that contains the chart information.
Delete the dump file you checked in step (5).
116
5.
Architecture
5.1
Process composition
HTTP/HTTPS
HTM Agent
HTTP/HTTPS
Action Handler
Trap Generator
HTTP/HTTPS
Agent Collector
Name Server
Agent Store
Correlator
Tuning Service
PFM NS API
Master Manager
Web Container (HBase)
HTM Agent
Tuning Manager MC
HSSO LIB
JDBC
Master Store
Action Handler
View Server
Agent Collector
PFM NS API
HiRDB
RMI
Web Container (HBase)
Agent Store
Status Server
Performance Reporter
Figure 5.1-1 Process composition of HTM (In Ver.6.0.0 to earlier than 8.0.0)
Table 5.1-1 Explanation of process (In Ver.6.0.0 to earlier than 8.0.0)
#
Explanation
Hitachi
Storage
Command
Hitachi
Storage
Command
Hitachi
This service provides the interface for getting data from Agent
Storage
Command
Suite TuningService
Hitachi
Storage
Command
117
Suite TuningManager
Performance Reporter
the
defined
information,
providing
defined
10
PFM - Correlator
11
12
13
14
Agent Collector
15
Agent Store
This service manages Agents DB, stores the data got by Agent
Collector.
16
[Note] In the figure 5.1-1, the process of Device Manager is drawn. This is because the
service of Device Manager is required to be running when
[Single Sign On] mode is used for Tuning Manager server. If not running, user cannot
log in to Tuning Manager server.
118
Explanation
1.
2.
3.
Service
4.
5.
Service
Hitachi
Command
TuningManager
Suite
119
Performance Reporter
7.
8.
the
defined
information,
providing
defined
10.
PFM - Correlator
11.
12.
13.
14.
Agent Collector
15.
Agent Store
This service manages Agents DB, stores the data got by Agent
Collector.
16.
120
Figure 5.1-3 Process composition of HTM (Version 8.1.3 to earlier than Version 8.2.1)
Table 5.1-3 Explanation of process (Version 8.1.3 to earlier than Version 8.2.1)
#
Explanation
Service
Service
121
Hitachi
Command
TuningManager
Suite
Performance Reporter
the
defined
information,
providing
defined
10
PFM - Correlator
11
12
13
14
Agent Collector
15
Agent Store
This service manages Agents DB, and stores and returns the
data obtained by Agent Collector.
If the data storage format is Hybrid Store, this service serves
as a compatibility service. This service obtains and returns the
data managed by Agent Rest Service.
16
122
Explanation
1.
2.
Service
4.
5.
Service
Hitachi
Command
Suite
123
TuningManager
6.
Performance Reporter
7.
8.
the
defined
information,
providing
defined
10.
PFM - Correlator
11.
12.
13.
14.
Agent Collector
15.
TCP/IP Collector
This process exists only when Agent for RAID uses TCP/IP
connections to collect performance data. This process collects
performance data using TCP/IP connections and output the
data to performance information files.
16.
Reciever
This process exists only when Agent for RAID uses TCP/IP
connections to collect performance data. This is a process for
communication
between
Agent
Collector
and
TCP/IP
Collector.
17.
Agent Store
This service manages Agents DB, and stores and returns the
data obtained by Agent Collector.
If the data storage format is Hybrid Store, this service serves
as a compatibility service. This service obtains and returns the
data managed by Agent Rest Service.
18.
124
5.2
Communication Sequence
5.2.1
?-NR
Master Manager
Master
started
Master Store
Manager
?-NI
?-PIT
Register
service
information
the
id
?-NI
?-PIT
R-PIT
?-AD
?-AD
?-DIC
R-DIC
125
Name Server
Master Manager
Correlator
?-NI
?-EAR
A-NI
Register the Service
ID information
?-EER
Action Handler
R-EER
Correlator started
?-NI
?-PIT
R-PIT
R-ACT
Register
the
event information
126
Small:Handler
6GB
Action
started
Medium: 6GB
Name Server
Master Manager
Correlator
Trap Generator
?-NI
Agent Store
?-NI
?-PIT
enough
space check)
Make sure that there is
F
(Disk
Agent Store started
127
Name Server
Master Manager
Agent Store
Agent Collector
?-NI
?-NI
E-AR
Correlator
?-ALM
?-DIC
#8 Check
?-PIT
128
5.2.1
Common-part initialization
thread
Startup request
Initialize UI layer
common part
Start
[Error Example]
If a property file that is available to users contains an
invalid property, the KATN17005-E message is output to
log files (htmMessage.log/ and htmTrace.log) or
the syslog/ event log. If a property file that is not
available to users contains an invalid property, the
KATN17015-E message is output to log files
(htmMessage.log and htmTrace.log) or the
syslog/ event log.
[Cause of the Error]
A property contains an invalid value in the property file
shown in the message.
Start
End
End
No
Has
the
core been
initialized?
Yes
Initialize HTnM UI layer
Figure 5.2.2-1 Overview of the startup sequence for the Tuning Manager server
129
[Error Example]
If the startup of Collection Manager or Performance Reporter
fails, the KATN10011-E message is output to log files
(htmMessage.log and htmTrace.log), and the
KATN10009-E message is output to the login window.
Sart up Collection
Manager
Attempt to start up
Performance Reporter
Initialize hibernate
Initialize various
features
[Error Example]
If a connection to HDvM cannot be established, the
KATN15014-E
message
is
output
to
log
files
(htmMessage.log/htmTrace.log) and the login window.
[Cause of the Error]
This error might be due to one of the following:
- The htm-dvm-setup command was not executed.
- The htmsetup command was not executed from the instance of
HDvM that is trying to be connected to.
- The instance of HDvM that is trying to be connected to is not
running.
[Startup Retry Interval]
If a startup check fails, up to 19 retries are made, once every 30
seconds (default).
End
130
For details on how to start or stop Tuning Manager server services, see the manual.
6.2.
Unused numbers
6.3.
HiRDB services
For details on how to start or stop HiRDB services, see the manual. If you are using the
Windows version, do not start and stop the service below.
Service:
[ In Ver.6 to earlier than 8 ]
- HiRDB/EmbeddedEdition _HD0
[ In Ver.8 or later ]
- HiRDB/EmbeddedEdition _HD1
This service is not used for starting or stopping HiRDB services. It is used for
controlling HiRDB services and needs to run continuously.
6.4.
Agent services
131
The following shows an example of starting the RAID Agent services whose instance name is
9970v.
(A) Open the Services window.
(B) Start the following services:
- PFM-Agent Store for RAID 9970v
- PFM-Agent for RAID 9970v
132
7. Other Information
7.1.
In version 6 or later, either IPv6 or IPv4 can be used as the protocol for communication between
Collection Manager and the Agent. In an environment in which both protocols are enabled, IPv6 has
precedence.
To use IPv4 in an environment in which both protocols are enabled, use the jpcnsconfig ipv6
command to disable IPv6. The following describes the procedure for disabling IPv6.
In Unix
/opt/jp1pc/tools/ jpcnsconfig ipv6 disable
KAVE05932-I The function for IPv6 communication will now be set up. (disable)
KAVE05933-I The function for IPv6 communication was successfully set up. (disable)
disable
In Unix
/opt/jp1pc/tools/ jpcnsconfig ipv6 display
disable
Note:
To enable IPv6, execute the jpcnsconfig ipv6 command with enable specified. The following shows
examples of executing the command:
In Windows
Suite-installation-directory\TuningManager\jp1pc\tools\ jpcnsconfig ipv6 enable
KAVE05932-I The function for IPv6 communication will now be set up. (enable)
KAVE05933-I The function for IPv6 communication was successfully set up. (enable)
In Unix
KAVE05932-I The function for IPv6 communication will now be set up. (enable)
KAVE05933-I The function for IPv6 communication was successfully set up. (enable)
7.2.
Caution when using Hitachi Tuning Manager with IE 6.0, IE 7.0 or IE 8.0 (Ver.6
to earlier than 8)
When using Hitachi Tuning Manager with IE 6.0, IE 7.0 or IE 8.0, a very rare phenomenon
might occur in which an additional invalid window is simultaneously displayed when a valid
window or dialog box is opened. The invalid window might resemble the opened window or
might be a blank window. This phenomenon does not impact succeeding operations. Please close
the invalid window, and then continue the operation. Note that this phenomenon occurs more
frequently in certain environments. Countermeasures that can reduce the frequency of this
phenomenon are as follows:
- Stop other programs that are placing a heavy burden on the CPU.
- If you are using Web Client (IE 6.0, IE 7.0 or IE 8.0) on a machine running Hitachi Tuning
Manager server, use Web Client (IE6.0 or IE7.0) on a different machine.
- Turn on Hyper-Threading.
7.3.
Tuning Manger for Linux version 7.1 and later do not support linking to Tiered Storage Manager
because those versions do not support Tuning Service.
When Tiered Storage Manager is linked with Tuning Manager by using Tuning Service, the error
KATS63030-E may occur and fail the linkage. In that case, look for the following error message
in the Tuning Service logs(*1).
KAVY20024-E The specified Agent is not running. (AgentID = <Agent information>)
If this message is output, execute jpcctrl list command (*2) to confirm the status of the agent
displayed as <Agent Information>.
<Agent Information> is output by comma separated text format and includes the following items.
- Product ID
- Function ID
- Instance NO.
- Device ID
- Instance Name
- Host Name
- Node type
The information which consists of Product ID, Function ID, Instance NO., and Device ID is Service
ID. Service ID is necessary as an argument of jpcctrl list command.
In the case that the displayed status is "Inactive", execute Tiered Storage Manager linkage function
again after starting the agent. In other cases, execute Tiered Storage Manager linkage function again
134
a) Execute the following command (*2) to stop Tuning Manager server on the host where the Tuning
Manager server is installed (*3).
[For Windows]
<Common-Component-installation-folder>\bin\hcmdssrv /stop /server TuningManager
[For Solaris]
/opt/HiCommand/TuningManager/bin/hcmdssrv -stop -server TuningManager
b) Execute the following command (*2) to stop agents connected the Tuning Manager server on
each host where the agent is installed (*4).
[For Windows]
<Agent-installation-folder>\tools\jpcstop <servicekey> [inst=<instance name>]
[For UNIX]
/opt/jp1pc/tools/jpcstop <servicekey> [inst=<instance name>]
c) Execute the following command (*2) to start Tuning Manager server on the host where the
Tuning Manager server is installed.
[For Windows]
<Common-Component-installation-folder>\bin\hcmdssrv /start /server TuningManager
[For Solaris]
/opt/HiCommand/TuningManager/bin/hcmdssrv -start -server TuningManager
d) Execute the following command (*2) to start Tuning Service on the host where the Tuning
Manager server is installed.
[For Windows]
<Common-Component-installation-folder>\bin\hcmdssrv /start /server TuningService
[For Solaris]
/opt/HiCommand/TuningManager/bin/hcmdssrv -start -server TuningService
e) Execute the following command (*2) to start agents connected the Tuning Manager server on
each host where the agent is installed.
[For Windows]
<Agent-installation-folder>\tools\jpcstart <servicekey> [inst=<instance name>]
[For UNIX]
/opt/jp1pc/tools/jpcstart <servicekey> [inst=<instance name>]
The issue will not be resolved after this recovery or the message KAVY20024-E is not found in the
Tuning Service logs, see the following manual and execute the operation against KATS63030-E.
- In Ver.6
Hitachi Tiered Storage Manager Software Messages
135
- In Ver.7
Hitachi Command Suite Software Messages Guide
(*1) Tuning Service logs are output in the following folder.
Suite-installation-directory\TuningManager\TuningService\logs\htmts1.log
(*2) For the detail the commands, see the manual of HTnM.
(*3) Notice: When Tuning Manager server service is stopped, all functions of Tuning Manager
server, including polling, stop.
(*4) Notice: When an agent is stopped, all functions of the agent, including collecting data, stop.
7.4.
If the shared disk resource is failed over while the HiRDB service is running following a failure of
the hcmdsdbclustersetup command, HiRDB cannot start.
In this case, the recovery must be performed as follows by editing the HiRDB definition file, which
has not been released as a product.
Recovery procedure
Perform the following procedure only on the executing node in a cluster configuration.
(2) Make sure that the shared disk to which the database for Hitachi Storage Command Suite
products is to be migrated has enough free space to hold the database. If there is not enough free
space, secure more free space.
136
To ensure that the HiRDB service will start successfully, change only this entry. Changing other
entries might cause startup of the HiRDB service to fail.
(6) Use the following command to confirm that the HiRDB service has started.
[ In Ver.6 to earlier than 8 ]
hcmdsdbsrv /status
[ In Ver.8 or later ]
hcmds64dbsrv /status
If the following message is output, the HiRDB service has started:
KAPM06440-I The HiRDB service has already started. is output.
(7) Re-execute the following command by specifying the options that were used when the previous
execution failed.
[ In Ver.6 to earlier than 8 ]
hcmdsdbclustersetup /createcluster /databasepath I:\share\HiCommand\HiRDB /exportpath
D:\HiCommand\work /auto
[ In Ver.8 or later ]
hcmds64dbclustersetup /createcluster /databasepath I:\share\HiCommand\HiRDB /exportpath
D:\HiCommand\work /auto
7.5.
Caution for the case that HTnM is connected to HDvM 6.0.0 to 6.1.1 and is monitoring an
SMS series subsystem
The prerequisite version of HDvM for monitoring SMS series is 6.2.0 or later. If the following
conditions are met, SMS subsystem cannot be monitored by HTnM. Therefore the recovery
procedure described below should be executed.
Conditions
137
(1) Under the combination of HTnM 6.2.0 or later and HDvM 6.0.0 to 6.1.1, an Agent for RAID
monitors an SMS series subsystem.
(2) While monitoring an SMS series subsystem in condition (1), Auto Migration is executed on the
subsystem.
(3) After (2), refreshing HDvM and HTnM polling are executed.
Recovery procedure
< Unless you are executing polling in connecting Agent for Server system that monitors a host
that SMS series connected to, skip the steps (6) and (7) below and continue executing the
procedure from the step (8). >
(6) Delete the service information of the Agent for Server System that monitors host connected to
SMS. For how to delete a service information, refer to the Hitachi Tuning Manager software
Agent Administration Guide.
(7) Perform a manual polling an hour or more after the last polling.
(8) Add an Agent for RAID and an Agent for Server System. About the way to add the agents, refer
to the Hitachi Tuning Manager software Server Administration Guide.
(9) Confirm gathered PD records. With Performance Reporter, you can confirm that reconnected
Agent for Server system and Agent for RAID have gathered PD records correctly.
(10) Perform a manual polling an hour or more after the last polling.
7.6.
Using the jpcctrl delete command with the force option (this option is in
non-public to user), to forcibly delete node information
To remove an Agent from the group of Agents monitored by Tuning Manager Server, you must use
the jpcctrl delete command to delete the service information for the Agent managed by Collection
138
Manager, as described in the Deleting Service Information section of the following manual:
[ manual ]
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
Before using the normal jpcctrl delete command to delete the service information for the Agent (as
instructed in the manual), if the Agent host is disconnected from the network that the Agent uses to
communicate with the host on which Tuning Manager Server is installed, you cannot use the jpcctrl
delete command to delete the service information.
In such a case, the force option which is in non-public to users must be specified for the jpcctrl
delete command to forcibly delete the service information for the Agent managed by Collection
Manager.
This section describes how to use the jpcctrl delete command with the force option.
Conditions
You can only use the jpcctrl delete command with the force option to delete Agent service
information if both of the following conditions are met:
Note: If you perform the jpcctrl delete command with the force option except both of the following
conditions View Server service in Collection Manager may fail start.
For details, see Log Information Analysis Guide [Appendix 2 FAQ] #38.
(1) The Agent service monitored by Tuning Manager Server is running on a different host from the
host on which Tuning Manager Server is installed.
(2) The Agent host is disconnected from the network that the Agent uses to communicate with the
host on which Tuning Manager Server is installed.
Recovery procedure
Use the jpcctrl delete command with the force option to forcibly delete the service information for
the Agent managed by Collection Manager.
Example:
In the following example, the jpcctrl delete command with the force option to delete the Agent
service information from the database managed by Collection Manager.
These examples assume that the following items.
- The name of the host running Tuning Manager Sever is "host01".
139
delete
host=
C44A1DE6A63543D -force
In UNIX:
# /opt/jp1pc/tools/jpcctrl delete "*" host= C44A1DE6A63543D -force
Note1:
If the above conditions cannot be met, we recommend that you do not use the force option. Before
you reconnect the Agent to the network that it uses to communicate with the host on which Tuning
Manager Server is installed, you must stop the Agent that is running on the Agent host.
If the above conditions are not met and you attempt to execute the command, the Agent service
information managed by Collection Manager might become corrupt. This can lead to the destruction
of the database managed by Collection Manager. If the database managed by Collection Manager is
destroyed, the View Server service will be unable to start. As a result, user attempts to log in to
Tuning Manager Server might fail.
Note2:
If the above conditions are met, and you execute the jpcctrl list command on a host that is running
Tuning Manager Server, the target Agent services are listed. The [Data Polling] window of Tuning
Manager Server also lists the Agent services on the target Agent host. If you attempt to perform
polling by the Tuning Manager Server, a failure occurs that results in an error, such as
KATN14864-E.
140
Example:
In the following example, the jpcctrl list command output and the Data Polling window for Tuning
Manager Server.
These examples assume that the following items.
- The name of the host running Tuning Manager Sever is "host01".
- The name of Agent host running Tuning Manager Sever is "C44A1DE6A63543D".
- The Agent host is disconnected from the network it uses to communicate with the host that runs
Tuning Manager Sever.
Host Name
ServiceID
-----------------
Service Name
PID
-------------------- -------- --------
Port
Status
host01
PT1host01
Status Server
1896
22350
Active
host01
PN1001
Name Server
5352
22285
Active
host01
PM1001
Master Manager
4384
1776
Active
host01
PS1001
Master Store
2280
1782
Active
host01
PE1001
Correlator
6624
1788
Active
host01
PC5host01
Trap Generator
3320
1795
Active
host01
PP1host01
View Server
2940
1853
Active
host01
PH1host01
Action Handler
1100
1436
Active
C44A1DE6A63543D ES1C44A1DE6A63543D Agent Store
620
1451
Active
C44A1DE6A63543D EA1C44A1DE6A63543D Agent Collector 2556
1455
Active
C44A1DE6A63543D TS1C44A1DE6A63543D Agent Store
4072
1475
Active
C44A1DE6A63543D TA1C44A1DE6A63543D Agent Collector 5324
1476
Active
KAVE06003-I List processing of the service information terminated normally.
Figure 7.6-2: Output when jpcctrl list "*" host="*" is executed on a machine running Tuning
Manager Server
Figure 7.6-1: Data Polling window for the Tuning Manager Server
141
142
6.2.0
6.2.0-00
6.4.0 or later
6.1.0
6.2.0-02
6.2.0-01
6.2.0-00
Product version
Upgraded from:
6.0.0
6.3.0
6.1.0
6.0.0
6.2.0
6.2.0-01
6.2.0-02
6.3.0
143
<Combinations of Agent versions for which this problem occurs(HTnM - Agent for
Server System)>
Product version Upgraded to:
6.2.0
6.4.0 or later
6.1.0
6.2.0-02
6.2.0-01
6.2.0-00
Product version
Upgraded from:
6.0.0
6.3.0
6.1.0
6.0.0
6.2.0
6.2.0-00
6.2.0-01
6.2.0-02
6.3.0
6.2.0
6.2.0-00
6.4.0 or later
6.1.0
6.2.0-02
6.2.0-01
6.2.0-00
Product version
Upgraded from:
6.0.0
6.3.0
6.1.0
6.0.0
6.2.0
6.2.0-01
6.2.0-02
6.3.0
144
7.7.1.4 Prerequisites
The following conditions must be met to use the Store database error detection tool:
(1) Prerequisite Programs
HTnM Server, HTnM Agents 6.0.0-00 or later is required.
(2) Required disk space
The following table shows the amount of disk space required to use the Store database
error detection tool.
Table 7.7-1: Disk space required to use the tool
Location
be checked
the
HTnM
products
30 MB x number-of-Store-databases-to-check#2
installation directories
#1: If the disk contains multiple Store database directories, the required disk space is equal
to the size of the largest Store database data file. For example, if Agent A has a 100 MB
data file, Agent B has a 150 MB data file, and Agent C has a 200 MB data file, the
required disk space is 200 MB.
A Store database data file is generally equal to the total size of all the files under the Store
database directory. An OS command can be used to easily check the total size of the data
under a Store database directory.
145
#2: Usually, the amount of required disk space is not as much as the estimate in the table.
In extreme cases though, the estimate in the table might be necessary, depending on the
amount of corrupt data.
(3) Memory Requirements
The memory required for executing Store database error detection tool is 100 MB.
(4) Command execution permissions
To use the Store database error detection tool, you must have logged on with the following
account:
Windows
UNIX
root user
#1: In Windows 2008, use the management console to execute the Store database error
detection tool. Right-click the Command Prompt icon, and then select Run as
administrator to open a command prompt session with administrator permissions.
#2: The Store database error detection tool must be executed from the CD-ROM or
DVD-ROM. It is not supported to execute the command copied onto a local disk.
Table 7.7-2: Location of the Store database error detection tool (HTnM 6.4)
Ty OS
Folder
pe
Server
1
2
Windows 2003
<CD-ROM drive>\
Windows_2K3_2K8\Maintenance_Tool\Windows_2K3
Windows 2008
<CD-ROM drive>\
\Windows_2K3_2K8\Maintenance_Tool\Windows_2K8
Solaris
<CD-ROM drive>/Solaris/Maintenace_Tool
Windows 2003
<CD-ROM drive>\Windows_2K3\Maintenance_Tool
Windows 2003
<CD-ROM drive>\Windows-IPF_2K3\Maintenance_Tool
Agen
146
(IPF)
6
Windows 2008
<CD-ROM drive>\Windows_2K8\Maintenance_Tool
Windows 2008
<CD-ROM drive>\Windows-IPF_2K8\Maintenance_Tool
(IPF)
8
Solaris
<CD-ROM drive>/Solaris/Maintenace_Tool
Solaris(x64)
<CD-ROM drive>/Solaris-x64/Maintenace_Tool
10
AIX
<CD-ROM drive>/AIX/Maintenance_Tool
11
Linux
<CD-ROM drive>/Linux/Maintenance_Tool
12
Linux(IPF)
<CD-ROM drive>/Linux-IPF/Maintenance_Tool
13
HP-UX
<CD-ROM drive>/HP-UX/Maintenance_Tool
14
HP-UX(IPF)
<CD-ROM drive>/HP-UX-IPF/Maintenance_Tool
Table 7.7-3: Location of the Store database error detection tool (HTnM 7.0)
#
Ty
OS
Folder
Windows 2003
none(*)
Windows 2008
none(*)
Solaris
none(*)
Windows 2003
<DVD-ROM
pe
2
Agent
Server
drive>\AGENTS\HTNM\Windows_2K3\Maintenance_Tool
Windows 2008
<DVD-ROM
drive>\AGENTS\HTNM\Windows_2K8\Maintenance_Tool
Solaris
<DVD-ROM
drive>\AGENTS\HTNM\Solaris\Maintenance_Tool
Solaris(x64)
<DVD-ROM
drive>\AGENTS\HTNM\Solaris-x64\Maintenance_Tool
AIX
<DVD-ROM drive>\AGENTS\HTNM\AIX\Maintenance_Tool
Linux
<DVD-ROM
drive>\AGENTS\HTNM\Linux\Maintenance_Tool
10
Linux(IPF)
<DVD-ROM
drive>\AGENTS\HTNM\Linux-IPF\Maintenance_Tool
11
HP-UX(IPF)
<DVD-ROM
drive>\AGENTS\HTNM\HP-UX-IPF
\Maintenance_Tool
*: In HTnM version 7.0, if you want to use the tool on the server side, then use the tool
contained in the Agent DVD-ROM.
-
Command
data
will
become
corrupted.
(record
record-ID[, drawer =
summarization-unit])
If this message is output, then data will become corrupted if the data model
of the Store database is upgraded. In this case, see 7.7.3.2 to take appropriate
action.
(2) Cases in which the Store database error detection tool:
If a message, which is not the message described in Step 3 (1) (b), beginning
148
with [Error] is output to the output files, the Store database error detection tool
might have failed. In this case, see 7.7.5 to take appropriate action. After
solving the problem, run the tool again.
7.7.2.2 Notes
This section contains notes that are important to know before using the Store
database error detection tool.
(1) The Store database error detection tool can be used only when a Store service
is stopped.
(2) Do not execute any other PFM or HTnM PR commands while running the
Store database error detection tool.
(3) When running the Store database error detection tool in a logical host
environment:
To use the tool on an Agent in a logical host environment, run the tool from
the executing node.
If a Store service exists on the physical host of a standby node, run the tool
on the standby node. If this is the case and the shared disk is mounted on the
standby node, the database processing on the logical host will fail, either of
the error messages below will be output, and then the next target database
will begin being processed. The following messages do not affect the
performance of the Store database error detection tool and can be ignored:
[Error] Store version check processing failed. (rc = 211)
[Error] Backup processing failed. (rc = 211)
(4) If there is not enough disk space to run the Store database error detection tool,
the tool fails, and the following message is output:
[Error] Backup processing failed. (rc = 210)
If this happens, see 7.7.5.1 to take appropriate action.
(5) The following temporary directory is created directly under the directory of the
Store database whose data is checked:
fix12753_backup
Usually, this temporary directory is automatically deleted after the tool
finishes. However, sometimes, such as when the tool terminates with an error,
the directory might not be deleted. If this happens, manually delete the
directory.
(6) If a file system is being monitored by a virus-checking application, the amount
of system memory consumed might increase while the application is running. If
this happens, perform either of the following, and then run the Store database
149
Command line
cd <CD-ROM drive>\Windows_2K3_2K8\Maintenance_Tool\Windows_2K3
150
dir=C:\Program
Data has been
corrupted..
dir=C:\Program
dir=C:\Program
By viewing these results, you can see that data in the Store database has been
corrupted.
151
File
Suite-installation-directory\TuningManager\jp1pc\tools\log\fix12753_check_error.log{01|02}
The third and seventh lines show that the most recent data corruption occurred
on 2008/12/18.
(g) Minimizing the impact of data corruption on current operations
To minimize the impact of data corruption, continue current operations as
usual, but be aware of the fact that some report data that was generated on or
before 2008/12/18 might be invalid.
(2) Solaris 10
,<In Ver.6.4>
*)Note that the execution procedure in a Solaris environment that is described in
this section assumes that the CD-ROM drive is mounted to the /cdrom/cdrom0
directory.
# Command line
1 /usr/sbin/mount -F cdfs -r device-special-file-name /cdrom/cdrom0
(a) Log in
Log in to the host as the root user. Alternatively, use the su command to switch to
152
153
The third and seventh lines show that the most recent data corruption occurred
on 2008/12/18.
(f) Checking the output file
Open the following file:
# File
1 /opt/jp1pc/tools/log/fix12753_check_error.log{01|02}
154
The third and seventh lines show that the most recent data corruption occurred
on 2008/12/18.
(g) Minimizing the impact of data corruption on current operations
To minimize the impact of data corruption, continue current operations as
usual, but be aware of the fact that some report data that was generated on or
before 2008/12/18 might be invalid.
155
156
Platform
Windows
UNIX
items
1
OS
Windows 2003
Solaris 10
CPU
Sparcv9 1000MHz
Memory
1.97GB
2.0GB
number of instance
#1: "Data" refers to the Store database data files that will be checked.
Table 7.7-6:Estimated processing times (Solaris)
#
#1: "Data" refers to the Store database data files that will be checked.
157
7.7.5 Troubleshooting
7.7.5.1 If the Store database error detection tool fails
If the Store database error detection tool fails, check the messages output to the
specified files and the return codes to identify the cause of the problem, and then
take appropriate action. See 7.7.6.2 for the messages that might be output by the
command. Also, see 7.7.6.3 for the return codes output along with the messages.
7.7.5.2 If there is not enough disk space
Perform either of the following procedures if there is not enough disk space to
execute the Store database error detection tool:
1) Increase the disk space , and then re-execute the Store database trouble
detection tool.
Allocate sufficient free space on the disk shown in 7.7.1.4(2). Then, re-execute
the command.
2) Stop the Agent's Store service, and then re-execute the tool.
The amount of available disk space can be increased by stopping the Agent's
Store service. After stopping the Store service, re-execute the tool.
Item
158
Data type
File path
[In Windows]
been corrupted
Suite-installation-directory\TuningManager\jp1pc\tools\log\fix12753_
check_error.log{01|02}(*)
[In UNIX]
/opt/jp1pc/tools/log/fix12753_check_error.log{01|02}(*)
[In Windows]
might be corrupted
Suite-installation-directory\TuningManager\jp1pc\tools\log\fix12753_
in the future
check_warning.log{01|02}(*)
[In UNIX]
/opt/jp1pc/tools/log/fix12753_check_warning.log{01|02}(*)
*: Log data is output every time the Store database error detection tool is executed. Two
log files are output for each data type, and the maximum size of each file size is 1 GB.
Output is saved to the files in the following format.
Table 7.7-9: Format of the output files
#
1
Item
Date and time
Description
Local date and time when the log data was output. The format
is as follows:
yyyy/mm/dd hh:mm:ss
2
Service key
Instance name
Directory
Record name
Drawer
Start date#1
The starting date (in local time) of the time period in which the
data to be output exists. The format is as follows: yyyy/mm/dd
End date#1, #2
The ending date (in local time) of the time period in which the
159
160
7.7.6.2 Messages
(1) Message format
Messages are output in the following format.
message-text
output-location-of-message
output-message-explanation
(S) The system action is shown here.
(O) The action to be taken by the operator is shown here. If no action is required, this
item is omitted.
(2) List of messages
Processing agent. servicekey=service-key[, instance=instance-name]
[,lhost=logical-host-name]
Standard output
Error detection for the Agent or Agents will now begin.
(S) Continues processing.
Processing StoreDB. dir=directory
Standard output
Error detection for Store data bases will now begin.
(S) Continues processing.
Processing BackupDB dir=directory
Standard output
Error detection for backup files of Store data base will now begin.
(S) Continues processing.
Processing ImportDB. dir=directory
Standard output
Error detection for import files of Store data base will now begin.
(S) Continues processing.
161
162
[Warning] If data model version will be upgraded, then at least one data will be broken.
(record=record ID[, drawer=summarization-unit])
Standard error output
Data that might become corrupted in the future has been found.
(S) Continues processing.
(O) See 7.7.3.2 to take appropriate action.
[Error] Backup processing failed. (rc=return code)
Standard error output
The Store database failed to be backed up.
(S) Cancels processing of the Store database. If there are any unprocessed Store
databases, those Store databases are processed in order.
(O) See 7.7.6.3 (a) to identify the symptom that corresponds to the output return code.
After resolving the problem, run the Store database error detection tool again.
If the cause of the error cannot be identified, refer to the jpclog common log to check
if there are any error messages. If you are still unable to resolve the problem, see 7.7.5.2
to take appropriate action.
[Error] Store version check processing failed. (rc=return code)
Standard error output
An attempt to check the version of a Store database has failed.
(S) Stops processing of the Store database. If there are any unprocessed Store
databases, those Store databases are processed in order.
(O) See 7.7.6.3 (b) to identify the symptom that corresponds to the output return code.
After resolving the problem, run the Store database error detection tool again.
If the cause of the error cannot be identified, refer to the jpclog common log to check
if there are any error messages. If you are still unable to resolve the problem, see 7.7.5.2
to take appropriate action.
163
running.
(S) Stops processing.
The start, stop or setup command is being executed.
Standard error output
The Store database error detection tool cannot be used because the start, stop, or
setup command is running.
(S) Stops processing.
Error occurred while deleting directory directory : return-code
Standard error output
An attempt to delete a temporary directory has failed. If the temporary directory
cannot be deleted, the Store database error detection tool might fail because there is not
enough disk space. This does not have any effect on the tool other than the disk space.
(S) Continues processing.
(O) Delete the directory-name directory.
[Error] Store version is invalid. (Store Version=store-version)
Standard error output
The Store database version in the definition file for the database being processed is
invalid. The definition file might be corrupted.
(S) Continues processing.
(O) Check the definition file stored in the directory of the database being processed
(jpcsto.ini/STDOCT.DAT/STRULES.DAT). If you are still unable to resolve the
problem, contact maintenance personnel.
Failed to lock the db directory. (rc=return-code dir=directory)
Standard error output
An attempt to lock the Store database has failed. The jpcresto command might be
accessing the Store database.
(S) Stops processing.
(O) Make sure that the jpcresto command is not being executed, and then
re-execute the command.
165
Return
Error cause
code
1
Unknown
An argument is invalid.
10
100
104
200
210
10
211
11
222
12
223
13
255
(b) Return codes that are output with the following message:
[Error] Store version check processing failed. (rc= return-code)
Return
Error cause
code
1
-1
166
(c) Return codes that are output with the following message:
[Error] DB check processing fails. (rc= return-code)
Return
Error cause
code
1
An argument is invalid.
200
210
211
255
(d) Return codes that are output with the following message:
Error occurred while deleting directory directory : return-code
The return code of "rmdir" command is displayed. The code is different in each platform.
(e) Return codes that are output with the following message:
Failed to lock the db directory. (rc=return code dir=directory)
Return
Error cause
code
1
-1
Unknown
-73
167
hcmdssrv /stop
hcmdssrv -stop
hcmdsdbsrv /stop
hcmdsdbsrv -stop
Confirm whether other programs are connected to HiRDB by performing the following procedure:
Note that HiRDB connections to the HDvM host might remain even after the HTnM server service
has been stopped.
7.8.1 How to confirm whether other programs are connected to HiRDB by using Command
[In Windows]
1. Change current directory to "bin" directory of the install directory of Common Component
database.
[ In Ver.6 to earlier than 8 ]
cd /d Suite-installation-directory\Base\HDB\BIN
[ In Ver.8 or later ]
cd /d Suite-installation-directory\Base64\HDB\BIN
2. Execute the following command. (This command sets the environment variable that is necessary
for executing command of HiRDB.)
pdntcmd
After executing "pdntcmd" command, operate the following procedures a) d), then confirm that the
environment variable is set correctly.
a) Execute "set PATH" command to confirm that the following two paths are added to the result.
[ In Ver.6 to earlier than 8 ]
Suite-installation-directory\Base\HDB\BIN
Suite-installation-directory\Base\HDB\CLIENT\UTL
[ In Ver.8 or later ]
Suite-installation-directory\Base64\HDB\BIN
Suite-installation-directory\Base64\HDB\CLIENT\UTL
"set PATH" command and confirm that the paths are added.
[ In Ver.6 to earlier than 8 ]
set
PATH=Suite-installation-directory\Base\HDB\BIN;Suite-installation-directory\Base\HDB\CLIENT\UTL;%
PATH%;
[ In Ver.8 or later ]
set
PATH=Suite-installation-directory\Base64\HDB\BIN;Suite-installation-directory\Base64\HDB\CLIENT\U
TL;%PATH%;
b) Execute "set PDDIR" command and confirm that the result is following.
[ In Ver.6 to earlier than 8 ]
Suite-installation-directory\Base\HDB
[ In Ver.8 or later ]
Suite-installation-directory\Base64\HDB
< When the above character string is not defined in PDDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDDIR" command and confirm that the variable was defined correctly.
[ In Ver.6 to earlier than 8 ]
set PDDIR=Suite-installation-directory\Base\HDB
[ In Ver.8 or later ]
set PDDIR=Suite-installation-directory\Base64\HDB
c) Execute "set PDCONFPATH" command and confirm that the result is following.
[ In Ver.6 to earlier than 8 ]
Suite-installation-directory\Base\HDB\CONF
[ In Ver.8 or later ]
Suite-installation-directory\Base64\HDB\CONF
< When the above character string is not defined in PDCONFPATH variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDCONFPATH " command and confirm that the variable was defined correctly.
[ In Ver.6 to earlier than 8 ]
set PDCONFPATH=Suite-installation-directory\Base\HDB\CONF
d) Execute "set PDUXPLDIR" command and confirm that the result is following.
[ In Ver.6 to earlier than 8 ]
169
Suite-installation-directory\Base\HDB\UXPLDIR
[ In Ver.8 or later ]
Suite-installation-directory\Base64\HDB\UXPLDIR
< When the above character string is not defined in PDUXPLDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDUXPLDIR" command and confirm that the variable was defined correctly.
[ In Ver.6 to earlier than 8 ]
set PDUXPLDIR=Suite-installation-directory\Base\HDB\UXPLDIR
[ In Ver.8 or later ]
set PDUXPLDIR=Suite-installation-directory\Base64\HDB\UXPLDIR
e) Execute the following command to confirm whether other programs are connected to HiRDB:
pdls -d prc -a
Any programs that are connected to HiRDB are displayed in the PROGRAM column of the
command execution results. Refer to the table Character strings displayed in the PROGRAM
column after the pdls command is executed below for the meanings of the character strings
displayed in the PROGRAM column.
An execution example is shown in Example of pdls -d prc -a command execution results below in
Example of the pdls -d prc -a command execution results.
Character strings displayed in the PROGRAM column after the pdls command is executed
Character string
Connected program
Ver.6
htm
Ver.7 or later
htm@<IP address>
HBase - hostname
********
Unknown
HOSTNAME : 127.0.0.1(173037)
STATUS
PID
UID
GID
SVID
TIME PROGRAM
C-PID
C-GRP
L
1531
170
1532
1533
1534
_mlg
999999 ********
1535
_rdm
999999 ********
1552
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
1553
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1554
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
1555
sds01
135911 HBase-SFT5220-01
1388(127.0.0.1)
1560
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1561
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1562
sds01
121433 HBase-SFT5220-01
1388(127.0.0.1)
1563
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1564
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1565
sds01
121434 HBase-SFT5220-01
1388(127.0.0.1)
1566
sds01
135929 HBase-SFT5220-01
1388(127.0.0.1)
1567
sds01
135836 htm
1388(127.0.0.1)
1577
sds01
121509 Unknown
1388(127.0.0.1)
...
PID
UID
GID
SVID
TIME PROGRAM
C-PID
C-GRP
L
1531
1532
1533
1534
_mlg
999999 ********
1535
_rdm
999999 ********
...
171
1552
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
1553
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1554
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
1555
sds01
135911 HBase-SFT5220-01
1388(127.0.0.1)
1560
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1561
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1562
sds01
121433 HBase-SFT5220-01
1388(127.0.0.1)
1563
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1564
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1565
sds01
121434 HBase-SFT5220-01
1388(127.0.0.1)
1566
sds01
135929 HBase-SFT5220-01
1388(127.0.0.1)
1567
sds01
1388(127.0.0.1)
1577
sds01
121509 Unknown
1388(127.0.0.1)
PID
UID
GID
SVID
TIME PROGRAM
C-PID
C-GRP
L
1531
1532
1533
1534
_mlg
999999 ********
1535
_rdm
999999 ********
4316
sds01
5668
sds01
0(127.0.0.1)
3680
sds01
0(127.0.0.1)
5472
sds01
999999
460
sds01
6004
sds01
999999
2724
sds01
999999
4888
sds01
999999
5304
sds01
999999
...
172
4456
sds01
[In Solaris]
1. Change current directory to "bin" directory of the install directory of Common Component
database.
cd /opt/HiCommand/Base/HDB/bin
2. Execute the following command. (This command sets the environment variable that is necessary
for executing command of HiRDB.)
. ./pduxenv
After executing "pduxenv" command, operate the following procedures a) d), then confirm that the
environment variable is set correctly.
a) Execute "echo $PATH" command to confirm that the following path is added to the result.
/opt/HiCommand/Base/HDB/bin
b) Execute "echo $PDDIR" command and confirm that the result is following.
/opt/HiCommand/Base/HDB
< When the above character string is not defined in PDDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $PDDIR" command and confirm that the variable was defined correctly.
PDDIR=/opt/HiCommand/Base/HDB;export PDDIR
c) Execute "echo $PDCONFPATH" command and confirm that the result is following.
/opt/HiCommand/Base/HDB/conf
< When the above character string is not defined in PDCONFPATH variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $PDCONFPATH" command and confirm that the variable was defined correctly.
PDCONFPATH=/opt/HiCommand/Base/HDB/conf;export PDCONFPATH
d) Execute "echo $LD_LIBRARY_PATH" command and confirm that the result is following.
173
/opt/HiCommand/Base/HDB/lib
< When the above character string is not defined in PDUXPLDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $LD_LIBRARY_PATH" command and confirm that the variable was defined
correctly.
LD_LIBRARY_PATH=/opt/HiCommand/Base/HDB/lib;export LD_LIBRARY_PATH
e) Execute the following command to confirm whether other programs are connected to HiRDB:
pdls -d prc -a
Any programs that are connected to HiRDB are displayed in the PROGRAM column of the
command execution results. Refer to the table Character strings displayed in the PROGRAM
column after the pdls command is executed below for the meanings of the character strings
displayed in the PROGRAM column.
An execution example is shown in Example of pdls -d prc -a command execution results below in
Example of the pdls -d prc -a command execution results.
Character strings displayed in the PROGRAM column after the pdls command is executed
Character string
Connected program
Ver.6
htm
Ver.7 or later
htm@<IP address>
HBase - hostname
********
Unknown
HOSTNAME : 127.0.0.1(173037)
STATUS
PID
UID
GID
SVID
TIME PROGRAM
C-PID
C-GRP
L
1531
1532
1533
174
1534
_mlg
999999 ********
1535
_rdm
999999 ********
1552
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
1553
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1554
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
1555
sds01
135911 HBase-SFT5220-01
1388(127.0.0.1)
1560
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1561
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1562
sds01
121433 HBase-SFT5220-01
1388(127.0.0.1)
1563
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1564
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1565
sds01
121434 HBase-SFT5220-01
1388(127.0.0.1)
1566
sds01
135929 HBase-SFT5220-01
1388(127.0.0.1)
1567
sds01
135836 htm
1388(127.0.0.1)
1577
sds01
121509 Unknown
1388(127.0.0.1)
...
PID
UID
GID
SVID
TIME PROGRAM
C-PID
C-GRP
L
1531
1532
1533
1534
_mlg
999999 ********
1535
_rdm
999999 ********
1552
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
1553
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1554
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
...
175
1555
sds01
135911 HBase-SFT5220-01
1388(127.0.0.1)
1560
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1561
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1562
sds01
121433 HBase-SFT5220-01
1388(127.0.0.1)
1563
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1564
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1565
sds01
121434 HBase-SFT5220-01
1388(127.0.0.1)
1566
sds01
135929 HBase-SFT5220-01
1388(127.0.0.1)
1567
sds01
1388(127.0.0.1)
1577
sds01
121509 Unknown
1388(127.0.0.1)
[In Linux]
1. Change current directory to "bin" directory of the install directory of Common Component
database.
cd <Hitachi Command Suite Common Component installation directory>/HDB/bin
2. Execute the following command. (This command sets the environment variable that is necessary
for executing command of HiRDB.)
. ./pduxenv
After executing "pduxenv" command, operate the following procedures a) d), then confirm that the
environment variable is set correctly.
a) Execute "echo $PATH" command to confirm that the following path is added to the result.
<Hitachi Command Suite Common Component installation directory>/HDB/bin
b) Execute "echo $PDDIR" command and confirm that the result is following.
/opt/HiCommand/Base/HDB
< When the above character string is not defined in PDDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $PDDIR" command and confirm that the variable was defined correctly.
PDDIR=/opt/HiCommand/Base/HDB;export PDDIR
176
c) Execute "echo $PDCONFPATH" command and confirm that the result is following.
/opt/HiCommand/Base/HDB/conf
< When the above character string is not defined in PDCONFPATH variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $PDCONFPATH" command and confirm that the variable was defined correctly.
PDCONFPATH=<Hitachi Command Suite Common Component installation directory>/HDB/conf;export
PDCONFPATH
d) Execute "echo $LD_LIBRARY_PATH" command and confirm that the result is following.
/opt/HiCommand/Base/HDB/lib
< When the above character string is not defined in PDUXPLDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $LD_LIBRARY_PATH" command and confirm that the variable was defined
correctly.
LD_LIBRARY_PATH=<Hitachi
Command
Suite
Common
Component
installation
directory>/HDB/lib;export LD_LIBRARY_PATH
e) Execute the following command to confirm whether other programs are connected to HiRDB:
pdls -d prc -a
Any programs that are connected to HiRDB are displayed in the PROGRAM column of the
command execution results. Refer to the table Character strings displayed in the PROGRAM
column after the pdls command is executed below for the meanings of the character strings
displayed in the PROGRAM column.
An execution example is shown in Example of pdls -d prc -a command execution results below in
Example of the pdls -d prc -a command execution results.
Character strings displayed in the PROGRAM column after the pdls command is executed
Character string
Ver.7 or later
Connected program
htm@<IP address>
HBase - hostname
********
177
Unknown
HOSTNAME : 127.0.0.1(173037)
STATUS
PID
UID
GID
SVID
TIME PROGRAM
C-PID
C-GRP
L
1531
1532
1533
1534
_mlg
999999 ********
1535
_rdm
999999 ********
1552
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
1553
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1554
sds01
121441 HBase-SFT5220-01
1388(127.0.0.1)
1555
sds01
135911 HBase-SFT5220-01
1388(127.0.0.1)
1560
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1561
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1562
sds01
121433 HBase-SFT5220-01
1388(127.0.0.1)
1563
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1564
sds01
135834 HBase-SFT5220-01
1419(127.0.0.1)
1565
sds01
121434 HBase-SFT5220-01
1388(127.0.0.1)
1566
sds01
135929 HBase-SFT5220-01
1388(127.0.0.1)
1567
sds01
1388(127.0.0.1)
1577
sds01
121509 Unknown
1388(127.0.0.1)
...
PID
UID
GID
SVID
TIME PROGRAM
178
C-PID
C-GRP
L
1531
1532
1533
1534
_mlg
999999 ********
1535
_rdm
999999 ********
4316
sds01
5668
sds01
0(127.0.0.1)
3680
sds01
0(127.0.0.1)
5472
sds01
999999
460
sds01
6004
sds01
999999
2724
sds01
999999
4888
sds01
999999
5304
sds01
999999
4456
sds01
...
179
7.8.2 How to confirm whether other programs are connected to HiRDB from log file
In an environment where the HTnM server and a connection-destination HDvM are
running on different hosts, it might not be possible to stop the HiRDB service on the
HDvM host if the HTnM server Main Console is using HiRDB connection on the HDvM
host. If this is the case, you need to identify the corresponding HTnM server host to stop
the HTnM server service that is connecting to the destination HDvM host.
This section explains how to identify the HTnM server host that is connecting to the
destination HDvM host by viewing the files output by the HDvM hcmdsgetlogs
command.
Procedure 1:
Use the following file to see which Main Console HiRDB connections exist on the
HDvM host and the IP address of the corresponding HTnM server. It is necessary to
extract archived files to view this file.
For a Windows HDvM host:
[ In Ver.6 to earlier than 8 ]
[HiCommand_log.hdb\HDB_DetailLog\Initial\pdinfoget_<hostname>_init_0414182
746\pdinfoget.sysinf.######]
or
[HiCommand_log.hdb \HDB_DetailLog\Detail\PDDIR\spool\cnctusrdtl]
<Ver.6>
"C:\Program Files\HiCommand\Base\HDB\bin\pdprcsls"
HOSTNAME : <HDvM host name>(###)
NO
STATUS
PID
UID
GID
SVID
24
L(RUN)
5400
sds01
190205
htm
25
L(RUN)
4348
sds01
190205
htm
< Ver.7>
Main Console HiRDB connections
"C:\Program Files\HiCommand\Base\HDB\bin\pdprcsls"
HOSTNAME : <HDvM host name>(###)
NO
STATUS
PID
UID
GID
SVID
TIME PROGRAM
C-PID
C-GRP
24
L(RUN)
5400
sds01
190205
25
L(RUN)
4348
sds01
190205
180
[ In Ver.8 or later ]
HiCommand_log_64.hdb\HDB_DetailLog\Initial\pdinfoget_<hostname>_init_04141
82746\pdinfoget.sysinf.######]
or
[HiCommand_log_64.hdb\HDB_DetailLog\Detail\PDDIR\spool\cnctusrdtl]
Main Console HiRDB connections
"C:\Program Files\HiCommand\Base64\HDB\bin\pdprcsls"
HOSTNAME : <HDvM host name>(###)
NO
STATUS
PID
UID
GID
SVID
TIME PROGRAM
C-PID
C-GRP
24
L(RUN)
5400
sds01
190205
25
L(RUN)
4348
sds01
190205
/opt/HiCommand/Base/HDB/bin/pdprcsls
HOSTNAME : <HDvM host name>(###)
NO
STATUS
PID
UID
GID
SVID
TIME PROGRAM
C-PID
C-GRP
39
L(RUN) 17270
sds01
181500
htm
40
L(RUN) 17271
sds01
181501
htm
STATUS
PID
UID
GID
SVID
TIME
PROGRAM
C-PID
C-GRP
39
L(RUN) 17270
sds01
40
L(RUN) 17271
sds01
Note: In Ver.7, All IP addresses might not be displayed for IPv6. In that case, execute Procedure 2.
For a Linux HDvM host:
[ In Ver.7.1 to earlier than 8 ]
[HiCommand_log.hdb\HDB_DetailLog\Initial\pdinfoget_<hostname>_init_0414182
746\pdinfoget.sysinf.######]
or
[HiCommand_log.hdb\HDB_DetailLog\Detail\PDDIR\spool\cnctusrdtl]
181
/opt/HiCommand/Base/HDB/bin/pdprcsls
STATUS
PID
UID
GID
SVID
TIME
PROGRAM
C-PID
C-GRP
39
L(RUN) 17270
sds01
40
L(RUN) 17271
sds01
STATUS
PID
UID
GID
SVID
TIME
PROGRAM
C-PID
C-GRP
39
L(RUN) 17270
sds01
40
L(RUN) 17271
sds01
Note: In Ver.7 or later, All IP addresses might not be displayed for IPv6. In that case, execute Procedure 2.
Procedure 2 (In case you use V6, or in case you use IPv6 in V7.0):
Use the following file to acquire the IP address of the HTnM server host that is
connecting to the destination HDvM host. The IP address can be identified by
checking the port numbers used by the HTnM server connecting to HDvM.
For details on the port numbers used by the HTnM server when connecting to
HDvM, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
182
Proto
Local Address
Foreign Address
State
TCP
10.208.147.74:4409
10.208.141.200:22971
ESTABLISHED
TCP
10.208.147.74:4410
10.208.141.200:22966
ESTABLISHED
Remote Address
State
10.208.141.200.22904 64255
0 49640
0 ESTABLISHED
10.208.147.23.40891
10.208.141.200.22926 65279
0 49640
0 ESTABLISHED
Local Address
Remote Address
State
10.208.141.200.22904 64255
0 49640
0 ESTABLISHED
10.208.147.23.40891
10.208.141.200.22926 65279
0 49640
0 ESTABLISHED
183
Connection target
Brocade
ouilist_fos.dat
Brocade
(SMI Agent for EOS)
In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent
ouilist_eos.dat
In Solaris, Linux:
/opt/jp1pc/agtw/agent
184
006069
OS
Windows
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\<instance
name>\log\msglog*
Solaris, Linux
/opt/jp1pc/agtw/agent/<instance name>/log/msglog*
Table 7.9-3: Message output when the OUI codes are error-free
No
Message
Message type
OUI code is registered. (file=<path to the OUI codes file edited in step 2>, Information
code=<OUI code added in step 2>)
- If the OUI code added to the OUI codes file is correct, the above message is displayed.
185
- If the above message is not displayed, the OUI code added to the OUI codes file is incorrect. Table
7.9-4 shows the messages that may be output to the log file of a Switch Agent instance if an OUI
code is incorrect. Use the table to determine the cause of the error. Fix the cause of the error and
repeat the steps from step 1.
Table 7.9-4: Warning messages that may be output when registration of an OUI codes file fails, and solutions
No
Message
Message type
Cause
Solution
Perform an overwrite
installation of Switch
exist.
Agent.
(file=<file
file is incorrect.
name>,
line=<line
hexadecimal characters.
If not, correct the OUI
code.
4
maximum.
maximum
number of lines.
(file=<file
name>,
maximum_number_of_lines=1024)
1024.
5
OUI code.
186
If Switch Agent connects to SMI Agent for FOS, it determines whether the Brocade switch
(B-Model) is to be monitored based on its OUI code, as shown in Table 7.9-5.
Table 7.9-5: OUI codes used for determining whether a Brocade (SMI Agent for FOS) switch is to be monitored
when Switch Agent connects to it
Brocade
No
(B-Model)
6.0.0
OUI code
(#1)
00051E
006069
000533
0027F8
50EB1A
6.1.0
6.2.0
6.3.0-00
6.3.0-01
7.0.0
or later
7.1.0
or later
Legend:
Y: This OUI code can be monitored with Switch Agent.
N: This OUI code cannot be monitored with Switch Agent.
#1: For Windows versions only. Unix versions (Solaris/HP-UX/AIX) are not supported.
If Switch Agent connects to SMI Agent for EOS, it determines whether the Brocade switch
(M-Model) is to be monitored based on its OUI code, as shown in Table 7.9-6.
Table 7.9-6: OUI codes used for determining whether a Brocade (SMI Agent for EOS) switch is to be monitored
when Switch Agent connects to it
No
1
6.3.0
7.0.0
7.1.0
or later
Y
Legend:
Y: This OUI code can be monitored with Switch Agent.
N: This OUI code cannot be monitored with Switch Agent.
187
common functions is also installed. Because there can be only one instance of this component on
each host, it is shared by multiple Agents if multiple Agents are installed on the host.
You can use the jpctminfo command to check the version of Agent Common Component.
Example of executing the jpctminfo command (version 7.1.1 or later)
---------------------------------------------------------------------------------->jpctminfo agtd
PRODUCT Hitachi Tuning Manager - Agent for RAID
VERSION 7.1.1-00(07-11-00)
COMPONENT Agent Common
VERSION 7.1.1-00(07-11-00)
-----------------------------------------------------------------------------------
If a version fixes only problems of Agent Common Component, the PRODUCT VERSION may not
be modified but only the version number of Agent Common Component may be modified. In such
cases, use the jpctminfo command to check the VERSION for the Agent Common component.
Note, however, that if HTnM - Agents are installed on a host on which the HTnM - server is installed,
Agent Common Component is not installed, and Collection Manager is used instead.
Therefore, when the jpctminfo command is executed in this environment, COMPONENT displays
the Collection Manager version rather than the Agent Common version.
188
189
HTnM-Server
JDBC(type4)/Hibernate
RMI
HTnM-PR
HTnM-TS
VSA
(View Server Access)
PFM-SDK Lib
HDvM
AnalyticsTab
HTnM-MC
HiRDB
NS-API (TCP/IP)
PQL/Performance DATA
VSA
(View Server Access)
HiRDB
Configuration
Capacity
REST Accessor
http
RMI
HTnM-Server
HTnM-CM
Name Server
Node Management
PFM-SDK Lib
Master Manager
Main Server
PFM-SDK Lib
View Server
View I/F
Correlator
Event Processor
Trap Generator
SNMP
HC-Agent Store
PFM-SDK Lib
PFM-SDK Lib
PFM-SDK Lib
PFM-SDK Lib
Master Store
Alert Event Store
PFM-SDK Lib
Status Server
PFM-SDK Lib
Action Handler
Action Invoker
HC Agent
Collector
PFM-SDK Lib
StoreDB
PFM-SDK Lib
Alert Event
HTnM-Server
REST API Component
StoreDB
Service
Configuration
http
HTnM-Agents
PFM-SDK Lib
Status Server
PFM-SDK Lib
Agent Store
PFM-SDK Lib
Agent Collector
PFM-SDK Lib
Action Handler
HTnM-Agent
REST API Component
Monitored
Systems
StoreDB
Performance
Configuration
File
Figure 7.12.1-1 Overview of the internal architecture behind the Analytics tab
The Analytics tab is a part of the HDvM GUI, and receives configuration and performance
information from HDvM and HTnM. In particular, when receiving such information from HTnM,
the Analytics tab accesses the HTnM View Server by using the VSA (View Server Accesser)
contained in HDvM.
Note: As described above, the Analytics tab receives information by accessing an HTnM component.
Therefore, to use the functions of the Analytics tab, the HTnM service must be running. For versions
8.0 and later, if the Tuning Manager API is enabled and if the Identify Performance Problems wizard
is used to analyze the minute-by-minute performance information, the performance information is
acquired by accessing the Tuning Manager API.
Property file
File location
Description
1.
tuningmanager.properties
2.
server.properties
190
config.xml
vsa\conf
Configuration information
4.
configforclient.xml
For details about the above properties, see the following manual:
- In Ver.7
Hitachi Command Suite Software Installation and Configuration Guide
- In Ver.8
Hitachi Command Suite Installation and Configuration Guide
Notes:
The ownHost property can be specified in the config.xml and configforclient.xml files. The
ownHost property in both files must be set to the same value.
The ownPort property can also be specified in the config.xml and configforclient.xml files. However,
the ownPort property in each file must be set to a different value.
File location
Description
1.
WebServiceMessage.log.n
WebServiceTrace.log.n
logs
components
(including
the
Analytics tab).
(The log data to be stored includes the
log data that is output when HDvM
accesses the Tuning Manager server
191
HDvMtracen.log
trace.log
logs
3.
vsaTracen.log
vsaTraceForClientn.log
vsa/logs
4.
5.
msglog
[HTnM server]
nslog
jpclog
htmRestMessagen.log
htmRestTracen.log
htmRestErrorDetailn.log
7.
htmRestAgtMessagen.log
htmRestAgtTracen.log
(*1) n: Number
(*2) Requests that are output to the logs include requests from user programs, as well as requests from HDvM (the
Analytics tab and the Replication tab). For details about how to identify request sources, see section 7.12.4.
7.12.3 Troubleshooting
To use the functions of the Analytics tab properly, the settings related to the tab must be specified
correctly. Table 7.12.3-1 lists the settings related to the Analytics tab and explains symptoms that can
occur if these settings are specified incorrectly.
Table 7.12.3-1 Settings related to the Analytics tab and symptoms that can occur
No.
Settings
1.
System environment
settings
2.
3.
If you encounter a symptom such as one of those shown above while you are using the Analytics tab,
first, review the relevant settings. The following subsections provide more detailed information
about the points to be reviewed.
7.12.3.1.2 Communication settings on the servers (HDvM server, HTnM server, and HTnM
Agent)
A) Name resolution must be performed correctly on all of these servers.
Point to be reviewed:
Make sure that the host names of all servers, including the local server, are correctly
specified in the hosts file (or the jpchosts file) on every server. If a DNS server is used to
perform name resolution, make sure that information about every server is correctly
registered on the DNS server.
Action (example):
Correctly specify the host name and IP address of each server in the hosts file (or the
jpchosts file) on every server. Alternatively, register the correct host information on the
193
DNS server.
Note: Particularly in an environment in which an HTnM server or HTnM Agent computer
has multiple NICs, use the jpchosts file to specify the IP addresses that HTnM server and
HTnM Agent can use to communicate with each other. (For details, see 3.3.7 Example 6:
Unable to see any storage from Main Console due to a mistake in the network configuration
in the Hitachi Tuning Manager Log Information Analysis Guide.)
B) For servers that have a firewall enabled, the ports used by the HDvM and HTnM services
must be included in the firewall exceptions list.
Point to be reviewed:
Make sure that the port numbers used by the services are included in the firewall exceptions
list. For the ports used by the services, see the manuals of the respective products. (For
example, for the ports used by the HTnM service, see Ports used by a Tuning Manager
server in the Tuning Manager Software Server Administration Guide.)
Action (example):
Include the ports used by the HDvM and HTnM services in the firewall exceptions list.
htnm.servers
htnm.server.n.host
htnm.server.n.protocol
htnm.server.n.port
Point to be reviewed:
Review the values of the above properties.
Action (example):
Set the correct values for the properties, and then restart the HCS services.
B) In an environment in which HDvM server and HTnM server are installed on the same
computer, the default values specified in the tuningmanager.properties file must be the same
as the values that are in actual use. For example, the default port number specified in the
tuningmanager.properties file must be the same as the port number in actual use. If the
194
default values in that file and the values in actual use do not match, change the values in the
file to the values in actual use.
Point to be reviewed:
Check and compare the default values specified in the tuningmanager.properties file and the
values in actual use.
Action (example):
Set the correct values for the properties, and then restart the HCS services.
ownHost
ownPort
Point to be reviewed:
Review the values of the above properties.
Action (example):
Specify the correct values for the properties, and then restart the HCS services.
B) When you set a value for the ownHost or ownPort properties, make sure that you
completely remove the commented-out line from the properties file. (See case study
SD4884688.)
<!-- The IPv4 address or host name that can connect to the Tuning Manager management server is specified.
To change it, use the value specified in configforclient.xml file.
This line must be removed.
-->
<!-<param name="ownHost" value=host1"/>
-->
195
Point to be reviewed:
Check the instance settings. For example, after checking the LOGIF setting of each record,
execute the jpctdchkinst command. Then, in the execution results of the command, check the
instance settings.
Point to be reviewed:
Review the record-data collection interval.
196
7.12.3.3.3 Recovery from a problem that sometimes occurs when the Tuning Manager API is
disabled
When an operation to disable the Tuning Manager API is performed on the HTnM Agent host,
Analytics Tab sometimes fails to analize storage system performance and display error messages
in the following window:
1) The Overview window of the Identify Performance Problems wizard (messages:
KAIC15633-E and KAIC08850-E)
2) The Analyze MP Blades/Units window (messages: KAIC18468-E and KAIC08850-E)
3) The Storage Performance Analysis per Host window (messages: KAIC08850-E)
Although to review settings and refresh storage systems on HDvM in accordance with the
messages, when Analytics Tab cannot be recovered from the symptom, perform the Recovery
measure described below.
If you encounter a problem such as the one above, check whether the Symptoms and Conditions
of occurrence described below apply in the user environment.
Note:
Although HTnM provides a function for disabling the Tuning Manager API, it is assumed that
most users will want to keep the Tuning Manager API enabled. Therefore, only this document
describes how to identify and correct the problem.
Symptoms
1) On the Overview page of the Identify Performance Problems wizard, an attempt to
obtain storage information from HTnM fails, and error messages KAIC15633-E and
KAIC08850-E are displayed.
messages:
Unable to collect Tuning Manager data. (resource name = resourcename, metric name(s)
= metricname(s), cause = KAIC08850-E Information cannot be collected from Tuning
Manager. A connection to the agent from Tuning Manager could not be established. (host
name = host-name, agent host name = agent-hostname, agent name = agentname)) See
the cause message. (KAIC15633-E)
messages:
Unable to collect information from Tuning Manager. (host name = host-name, agent
197
3) The Storage Performance Analysis per Host window opens, an attempt to obtain storage
information from HTnM fails, and error message KAIC08850-E is displayed.
message:
Information cannot be collected from Tuning Manager. A connection to the agent from
Tuning Manager could not be established. (host name = host-name, agent host name =
agent-hostname, agent name = agentname) (KAIC08850-E)
Conditions of Occurrence
This symptoms occurs when both of the following conditions are met:
(1) In HDvM, a storage system that is monitored by an Agent instance for which the Tuning
Manager API is enabled is added or refreshed.
(2) After (1), an operation to disable the Tuning Manager API is performed on the Agent host.
Examples of operations that disable the Tuning Manager API include the following:
- Executing the htmrestctl off command
- Re-installing Agent (During installation, after the Store database is selected, an Agent
instance that monitors the storage system in (1) is re-created with the same name as the
instance in (1).)
Recovery
Perform the procedure below. For details about the commands used in the procedure, see the
Hitachi Command Suite Tuning Manager CLI Reference Guide.
1) Stop the instances that are running on the Agent host on which the Tuning Manager API is
disabled. You need to stop only the instances of the type that supports the Tuning Manager
API.
jpcstop agtd inst=Instance-name
2) On the HTnM server host, delete the services of the instances that you stopped in step 1.
jpcctrl delete Instance-name
3) On the HTnM server host, stop the HTnM server.
hcmds64srv /stop /server TuningManager
4) On the HTnM server host, start Collection Manager only.
jpcstart mgr
5) On the HTnM server host, start the Tuning Manager API service only.
hcmds64srv /start /server TuningManagerRESTService
6) On the HTnM server host, confirm that startup of the Tuning Manager API service has
198
finished.
hcmds64srv /status
7) On the HTnM Agent host, restart the Agent instances that you stopped in step 1.
jpcstart agtd inst=Instance-name
8) On the HTnM server host, confirm that the instance services that you restarted in step 7
exist.
jpcctrl list * host=*
9) On the HTnM server host, start the HTnM server.
hcmds64srv /start /server TuningManager
10) Refresh the storage system from HDvM.
7.12.4 How to examine the related logs (for versions 8 and later)
The Tuning Manager server outputs logs (*1) related to the Tuning Manager API. These logs
contain requests from HDvM (the Analytics tab and the Replication tab), as well as requests from
user programs.
When using the Tuning Manager API logs to analyze a problem that occurred in HDvM, check the
requests from HDvM first. Requests from HDvM contain the word internal in the URI. The
following table lists URI examples for requests from various sources.
(*1) htmRestMessagen.log, htmRestTracen.log, and htmRestErrorDetailn.log (where n represents a
number) listed in Table 7.12.2.2-1.
Table 7.12.3.4-1 Examples of URIs for requests
#
Request source
1. HDvM
URI example
http://127.0.0.1:22015/TuningManager/internal/v1/objects/AgentForRAID
http://127.0.0.1:22015/TuningManager/v1/objects/AgentForRAID
199
200
7.15 Performance data collection by using a TCP/IP connections for Agent for
RAID
7.15.1 If the microcode version of the monitored storage system is not supported
If the microcode version of the monitored storage system is earlier than the supported versions,
and you want to create an instance by using the jpcinssetup command, set 1: Command
Device for Method for collecting.
In the above case, if you select 3: Both for Method for collecting, and specify settings to collect
performance data by using a TCP/IP connections, Agent Collector will detect that the storage
system is not supported, and then stop the service. Because of this, performance data will not be
collected by command devices either.
To check if performance data collection using a TCP/IP connections is supported, execute the
jpctdchkinst command.
7.15.2 How acquisition of performance data is affected by a limit on the number of sessions
Multiple programs or users cannot simultaneously log in to or obtain performance data from a
storage system by using the same user ID. This is because sessions where a program or user can
log in to a storage system and obtain performance data are limited to one session for a given user
ID.
For this reason, if an Agent instance cannot obtain performance data using a TCP/IP connections
from a storage system, check if the following exist:
- Other programs (such as the Export Tool for Performance Monitor) that are collecting
performance data from the same storage system by using the same user ID
- Other Agent instances that monitor the same storage system by using the same user ID
After checking the above, stop any programs or Agent instances as needed.
201
7.15.3 Typical causes of failure in performance data collection using TCP/IP connections
The following table describes the typical causes of failure in performance data collection.
Table 7.15.3-1 Typical causes of failure in performance data collection when using TCP/IP
connections
#
Main cause
Section that
provides details
7.15.3.1
Other processes are logged in to a storage system with the same user ID
7.15.3.2
7.15.3.3
Memory is insufficient
7.15.3.4
In addition, if an Agent instance has already started, the following message will be output to a log
file.
Log file*
Details of output
pmmcChkSvpTrace[n].log
KATR25044-I I
Action to be taken:
Upgrade the microcode version of the monitored storage system to a supported version.
202
7.15.3.2 Other processes are logged in to a storage system with the same user ID
How to check this:
The following messages are output to log files.
Log file*
Details of output
pmmcChkSvpTrace[n].log
The following stack trace will be output together with an error message
pmmcGetdkcinfTrace[n].log
pmmcCollectorTrace[n].log
Action to be taken:
Stop other processes that are logged in to the storage system by using the same user ID.
Alternatively, use the jpcinssetup command to change the settings of the Agent instance so
that it can use another user ID to log in to the storage system, and then restart the instance.
7.15.3.3 Other processes are collecting performance data from a storage system
How to check this:
The following messages are output to log files.
Log file*
Details of output
pmmcChkSvpTrace[n].log
The following stack trace will be output together with an error message
pmmcGetdkcinfTrace[n].log
pmmcCollectorTrace[n].log
Action to be taken:
Check if the following exist:
- Other programs (such as export tools for Performance Monitor) that are collecting
performance data from the same storage system by using the same user ID
- Other Agent instances that monitor the same storage system by using the same user ID
After checking the above, stop any programs or Agent instances as needed.
203
Action to be taken:
Check whether the installed physical memory is sufficient. If the installed physical memory is
sufficient, execute the jpcinssetup command. In the Java VM Heap Memory setting, specify
a value greater than that currently specified for the Java heap memory size, and then restart the
Agent instance. For details about the memory size to be specified, see Hitachi Command Suite
System Requirements.
204
In Ver.7
In Ver.7.1
In Ver.8
Appendix1_V8_metri
cs.zip
205
This content was deleted, because it pertained to version 5 or earlier. To see this content, see the
documents for versions earlier than version 8.
3-b
Deleting Tuning Manager server for Windows (In Ver.6.0.0 to earlier than 8.0.0)
3-b.1
Purpose
This appendix provides an overview of deleting Tuning Manager server for Windows, and describes
the following procedures (which are not disclosed to users):
- Procedure for deleting Tuning Manager server without deleting Agent
- Procedure for forcibly deleting the Tuning Manager server manually
3-b.2
Applicable Versions
3-b.3
Figure 3-b.3-1 shows an overview of the process for deleting Tuning Manager server.
206
Start
Forcibly Deleting Tuning Manager server
Do you want to perform
an uninstallation that leaves
Agents?
NO
YES
NO
Was the uninstallation successful?
YES
Normal uninstallation procedure
NO
YES
YES
NO
End
Restarting the OS
End
End
Figure 3-b.3-1 The flow of the deletion of the Tuning Manager server
Notes:
-
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, use the deletion procedure described in 3-b.4. Do not use the forced
deletion procedure described in 3-b.5. If you do, all Hitachi Storage Command Suite products,
including Agent, will no longer start.
Only perform the forced deletion procedure described in section 3-b.5 if you cannot perform a
normal uninstallation.
Before you forcibly delete Tuning Manager server, make sure that Hitachi Storage Command
Suite family of products other than Tuning Manager server have not been installed. If such
products have been installed, uninstall them before forcibly deleting Tuning Manager server.
For details about how to uninstall a Hitachi Storage Command Suite product, see the
maintenance manual or other manuals for the product.
Because the forced deletion procedure edits the registry, special care is required.
207
The deletion procedure described in this document does not change the settings of Hitachi
Storage Command Suite family of products (including Agents), such as HiCommand Device
Manager, that are installed on hosts other than the host on which Tuning Manager server is
installed. To change the settings of such products, see the maintenance manual or other manuals
for the products.
If you are using a 64-bit OS, substitute the following folders and registry keys for the
corresponding notations used in the text.
#
1
2
3
208
On a 64-bit OS
%SystemRoot%\SysWow64
%ProgramFiles(x86)%
HKEY_LOCAL_MACHINE\SOFTWARE\
Wow6432Node
3-b.4
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, uninstall Tuning Manager server as described below.
Value to set
1
Figure 3-b.4-1: Window that appears when Tuning Manager server is successfully uninstalled
209
Note: If an error occurs during the deletion procedure in 3-b.4, integrity of the environment will
be lost. If such an error occurs, you might need to completely delete the environment by using
the forced deletion procedure in 3-b.5.
Note: This note applies when you install a Hitachi Command Suite products after deleting
Tuning Manager server as described in 3-b.4. In such a case, during installation, when you
specify the installation directory, make sure that you specify the directory in which Hitachi
Command Suite products, including the Tuning Manager server, were installed before you
deleted Tuning Manager server. If you specify a different directory, incorrect installation or
operation of the product might result.
210
3-b.5
6.0.0 or later
1.0.0-00
3-b.5.1
3-b.5.1.1
Terms
The following terms are used in this section.
#
1
Terms
Directory
Hitachi Storage
%ProgramFiles%\HiCommand\Base
Command-Suite-Common-Component-installation-directory
Hitachi-Tuning-Manager-installation-directory
%ProgramFiles%\HiCommand\TuningManager
installation-directory
%ProgramFiles%\HiCommand
Note: Unless you specify other directories during installation, the above
directories are used by default.
3-b.5.1.2
Directory
Command
hcmdssrv /stop
211
c) Execute the following command and make sure that stopped is displayed for the
displayed services, as shown in the output example below.
#
Command
hcmdssrv /status
Directory
Hitachi-Tuning-Manager-installation-directory\jp1pc\tools
Command
jpcstop all
If the message KAVE05000-E The specified service is not running is displayed, the
service is not running, so go to the next step.
Output example
KAVE06008-I The service will now stop. (service=Action Handler)
KAVE06008-I The service will now stop. (service=Trap Generator)
KAVE06008-I The service will now stop. (service=Correlator)
KAVE06008-I The service will now stop. (service=Master Store)
KAVE06008-I The service will now stop. (service=Master Manager)
KAVE06008-I The service will now stop. (service=Name Server)
KAVE06008-I The service will now stop. (service=Status Server)
212
f)
Execute the command indicated below and make sure that Inactive* is
displayed for the displayed services, as shown in the output example below.
If the jpcctrl command does not exist, go to step (2) in section 3-b.5.1.2.
Even if Inactive* is not displayed (and another string, such as Active, is displayed
Command
jpcctrl list *
ServiceID
---------
Service Name
-------------
--------
PID
--------
Port
Status
--------
XXXX
PT1XXX
Status Server
Inactive*
XXXX
PN1001
Name Server
Inactive*
XXXX
PM1001
Master Manager
Inactive*
XXXX
PS1001
Master Store
Inactive*
XXXX
PE1001
Correlator
Inactive*
XXXX
PCXXX
Trap Generator
Inactive*
XXXX
PP1XXX
View Server
Inactive*
XXXX
PH1XXX
Action Handler
Inactive*
HiRDB/ClusterService _HD0
HiRDB/EmbeddedEdition _HD0
10
11
12
PFM - Correlator
13
14
15
16
17
18
3-b.5.1.3
(1) Check the directory that stores the database for Hitachi Storage Command Suite
Common Component.
a) Open the file indicated below.
If the file does not exist, go to step (2) in section 3-b.5.1.3.
#
File Name
Hitachi Storage
Command-Suite-Common-Component-installation-directory\conf\hcmdsdbinit.ini
b) Write down the value of the initpath property (the database file directory)
specified in the file.
(2) Delete the Tuning Manager server registration information.
a) Open a command prompt, and then move to the following directory.
If the directory does not exist, go to step (4) in section 3-b.5.1.3.
214
Directory
Command
If
the
message
KAPM04202-I(the
command
executed
successfully)
or
Command
hcmdscancel TuningManager
File Name
%SystemDrive%\htmpruninst.rtn
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
(2) Execute the Collection Manager uninstaller (in Windows Server 2008).
a) Open a command prompt.
b) Open the following file by using a text editor.
#
1
File Name
Hitachi-Tuning-Manager-installation-directory\inst\cm_guid.dat
The character string in this file is the Collection-Manager-GUID.
If the file does not exist, go to section 3-b.5.1.5. If the file does not exist, some of the
information of Collection Manager might remain. Therefore, after forcibly delete
Tuning Manager server, perform the procedure described in section 3-b.5.1.12.
c) Start the registry editor.
From the Start menu, choose Run. In the displayed dialog box, enter regedit, and
then click the OK button to start the registry editor.
d) Use the registry editor to make sure that the registry key indicated below
exists.
If this registry key does not exist, go to section 3-b.5.1.5.
# Registry Key
216
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
<Collection Manager-GUID>
Command to execute
{UninstallString-command}/qn+
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
Note: Make sure that the Services applet is closed when executing the uninstaller.
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
Command to execute
{UninstallString-value}/NOREBOOTNOFLAGOFF (: a single-byte space)
Note: Make sure that the Services applet is closed when executing the uninstaller.
e) Open the following file and make sure that the termination status has been
output.
If the termination status has been output, the uninstallation has finished. Ignore
any other output values.
#
File Name
%SystemDrive%\htmpruninst.rtn
Note: If the file does not exist, the uninstallation is still in progress.
Note: Uninstallation might take five or more minutes to finish.
3-b.5.1.7 Uninstalling the Hitachi Storage Command Suite Common Component
(1) Execute the forced uninstallation command.
a) Copy the command indicated below to the root directory of the OS startup drive.
If the file does not exist, go to section 3-b.5.1.8.
#
1
File
Hitachi Storage
Command-Suite-Common-Component-installation-directory\tmp\HBuninst.exe
218
b) Open a command prompt, and then move to the root directory of the OS startup
drive.
c) Execute the command indicated below. Respond to all questions with Yes.
#
1
Command line
HBuninst /X
d) After the dialog box that indicates termination of the command appears, check
the value that was output to the following file.
#
1
File
root-directory-of-the-OS-startup-drive\hcmdsrtn.enf
If the value is 2, restart the OS, and then re-execute the command described in step (1)
c) in section 3-b.5.1.7.
If the value is not 2, or if the value is still 2 after re-execution, restart the OS, and then
go to section 3-b.5.1.8.
3-b.5.1.8
(4) Confirm the end code that appears after you execute the command.
Removal of the registry keys for HTnM Server has ended.
[End code: <end code>]
Press any key to continue.
(5) Refer to the end code and take the appropriate action.
If the end code is 1, open the file that is shown below and check the command
execution results. If you do not have administrator privileges, the log file might not be
output.
#
File name
%SystemDrive%\htnmsvrregclean.log
End
Error
Cause
Action
Registry
In
permission
deletion failed.
code
1
the
access
220
Delete Permission.
control
manager,
specify
privileges.
unelevated
An
Administrators
group,
and
group.
3-b.5.1.9
Reboot the OS
Reboot the OS
3-b.5.1.10 Deleting files and directories
(1) Delete the files shared by the Collection Manager components.
Make sure that the shared files indicated below do not exist.If these files exist,
delete them manually.
#
1
2
3
4
5
6
Note: The {vvrrss} part in the file names is a string of alphanumeric characters that
indicates the DLL version number.
(2) Delete the component install temporary directories that are shared by Hitachi
Storage Command Suite.
221
then
Directory
%temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
%SystemDrive%\_HDBInstallerTemp
File name
Hitachi-Tuning-Manager-installation-directory\inst\db_area.properties
Hitachi-Tuning-Manager-installation-directory\inst\db_area_6.properties
b) In these files, check the values of the properties indicated below, which indicate
the database file directories. Note that the db_areapath2 property might not be
specified in the file.
#
Property Name
db_areapath1
db_areapath2
Directory
<Installation directory>
222
Directory
Command line
hcmdsintg /print /user "htnmrepuser"
( represents a one-byte space)
/pass
"INTERNALHRXJIHVZ"
223
Command line
hcmdsintg /delete /type TuningManager /user "htnmrepuser"
"INTERNALHRXJIHVZ"
( represents a one-byte space)
/pass
d) Execute the command indicated below. Make sure that TuningManager is not
included in the output results.
#
Command line
hcmdsintg /print /user "htnmrepuser"
( represents a one-byte space)
/pass
"INTERNALHRXJIHVZ"
3-b.5.2
3-b.5.2.1
Terms
The following terms are used in this section.
Terms
Directory
Hitachi Storage
%ProgramFiles%\HiCommand\Base
1
Command-Suite-Common-Component-installation-directory
2
Hitachi-Tuning-Manager-installation-directory
%ProgramFiles%\HiCommand\TuningManager
installation-directory
%ProgramFiles%\HiCommand
Note: Unless you specify other directories during installation, the above directories are
224
used by default.
3-b.5.2.2
Directory
Command
hcmdssrv /stop
c) Execute the following command and make sure that stopped is displayed for the displayed
services, as shown in the output example below.
#
Command
hcmdssrv /status
Note: Depending on the uninstallation status, some services might not be displayed.
Note: If stopped is still not displayed for hcmdssrv /status 10 minutes after executing
hcmdssrv /stop, go to step (1) d) in section 3-b.5.2.2.
d) Move to the directory indicated below.
If the directory does not exist, go to step (2) in section 3-b.5.2.2.
#
Directory
Hitachi-Tuning-Manager-installation-directory\jp1pc\tools
225
Command
jpcstop all
If the message KAVE05000-E The specified service is not running is displayed, the service is
not running, so go to the next step.
Output example
KAVE06008-I The service will now stop. (service=Action Handler)
KAVE06008-I The service will now stop. (service=Trap Generator)
KAVE06008-I The service will now stop. (service=Correlator)
KAVE06008-I The service will now stop. (service=Master Store)
KAVE06008-I The service will now stop. (service=Master Manager)
KAVE06008-I The service will now stop. (service=Name Server)
KAVE06008-I The service will now stop. (service=Status Server)
Note: Depending on the uninstallation status, some services might not be displayed.
f)
Execute the command indicated below and make sure that Inactive* is displayed for the
displayed services, as shown in the output example below.
If the jpcctrl command does not exist, go to step (2) in section 3-b.5.2.2.
Even if Inactive* is not displayed (and another string, such as Active, is displayed instead),
Command
jpcctrl list *
If the message KAVE05024-E The specified service is not registered. is displayed, the service
is not running, so go to the next step.
Example of the output
Host Name
---------
ServiceID
---------
Service Name
-------------
--------
PID
--------
Port
Status
--------
XXXX
PT1XXX
Status Server
Inactive*
XXXX
PN1001
Name Server
Inactive*
XXXX
PM1001
Master Manager
Inactive*
XXXX
PS1001
Master Store
Inactive*
XXXX
PE1001
Correlator
Inactive*
XXXX
PCXXX
Trap Generator
Inactive*
XXXX
PP1XXX
View Server
Inactive*
XXXX
PH1XXX
Action Handler
Inactive*
Note: Depending on the uninstallation status, some services might not be displayed.
Note: The asterisk (*) in Inactive* might not be displayed.
226
(2) Change the startup type for Hitachi Storage Command Suite-related services.
a) Start the Services applet.
b) Change the startup type to Manual for all of the following Hitachi Storage Command
Suite-related services. You can change the startup type from the Service Properties dialog
box.
Note: Depending on the uninstallation status in section 3-b.4, some services might not be
displayed.
Note: The startup type will already be set to Manual for some services.
#
HiRDB/ClusterService _HD0
HiRDB/EmbeddedEdition _HD0
10
11
12
PFM - Correlator
13
14
15
16
17
18
(1) Check the directory that stores the database for Hitachi Storage Command Suite Common
Component.
a) Open the file indicated below.
227
File Name
b) Write down the value of the initpath property (the database file directory) specified in the
file.
(2) Delete the Tuning Manager server registration information.
a) Open a command prompt, and then move to the following directory.
If the directory does not exist, go to step (4) in section 3-b.5.2.3.
#
1
Directory
Hitachi Storage Command-Suite-Common-Component-installation-directory\bin
Command
Command
hcmdscancel TuningManager
File Name
%SystemDrive%\htmpruninst.rtn
3-b.5.2.4
If you are using Windows Server 2003, perform the procedure described in step (1) in section
3-b.5.2.4. If you are using Windows Server 2008, perform the procedure described in step (2) in
section 3-b.5.2.4.
(1) Execute the Collection Manager uninstaller (in Windows Server 2003).
a) Open a command prompt.
b) Start the registry editor.
From the Start menu, choose Run. In the displayed dialog box, enter regedit, and then click the
OK button to start the registry editor.
c) Use the registry editor to make sure that the registry key indicated below exists.
If this registry key does not exist, go to step (4) in section 3-b.5.2.4.
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
(2) Execute the Collection Manager uninstaller (in Windows Server 2008).
a) Open a command prompt.
b) Open the following file by using a text editor.
229
File Name
Hitachi-Tuning-Manager-installation-directory\inst\cm_guid.dat
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
<Collection Manager-GUID>
Paste the copied value into the command prompt, add the following option, and then
execute the command. The uninstallation will start.
Command to execute
{UninstallString-command}/qn+
Note: If the uninstallation terminates successfully, the following dialog box indicating such
is displayed. Click OK to close the dialog box.
Note: Make sure that the Services applet is closed when executing the uninstaller.
g) After executing the uninstaller, go to step (3) in section 3-b.5.2.4.
If The uninstallation of Collection Manager fails, some of the information of Collection
Manager might remain. Therefore, after forcibly delete Tuning Manager server, perform the
procedure described in section 3-b.5.2.12.
(3) Make sure that Collection Manager has been uninstalled.
a) Make sure that the registry keys indicated below do not exist.
If these registry keys exist, delete them manually.
#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGT0(The last value is a zero.)
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_0A(The
second to last character is a zero.)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_0S(The
second to last character is a zero.)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PC
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PE
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PH
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PM
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PN
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PP
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PT
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
Application\PFM
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
Application\PFM-HealthCheck
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
Note: If other Hitachi Storage Command Suite products have been installed, the registry
key name Hitachi might be displayed as HITACHI (in all upper-case letters).
b) Make sure that the shared files indicated below do not exist.
If these files exist, delete them manually.
#
1
2
3
4
5
6
Note: The {vvrrss} part in the file names is a string of alphanumeric characters that indicates
the DLL version number.
231
3-b.5.2.5
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
Registry Key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
1
HiCommandTuningService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\
2
HTM-Tuning Service
3
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
3-b.5.2.6
Registry Key
232
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
Command to execute
{UninstallString-value}/NOREBOOTNOFLAGOFF (: a single-byte space)
Note: Make sure that the Services applet is closed when executing the uninstaller.
e) Open the following file and make sure that the termination status has been output.
If the termination status has been output, the uninstallation has finished. Ignore any other output
values.
#
File Name
%SystemDrive%\htmpruninst.rtn
Note: If the file does not exist, the uninstallation is still in progress.
Note: Uninstallation might take five or more minutes to finish.
(2) Make sure that the registry keys indicated below do not exist.
a) Make sure that the registry keys indicated below do not exist.
If these registry keys exist, delete them manually.
# Registry Key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
1
PerformanceReporter
(When x86 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\HTMPR
2
(When x64 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\HTMPR
3
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
Note: If other Hitachi Storage Command Suite products have been installed, the registry
key name Hitachi might be displayed as HITACHI (in all upper-case letters).
3-b.5.2.7
#
1
File
Hitachi Storage
Command-Suite-Common-Component-installation-directory\tmp\HBuninst.exe
b) Open a command prompt, and then move to the root directory of the OS startup drive.
c) Execute the command indicated below. Respond to all questions with Yes.
#
1
Command line
HBuninst /X
d) After the dialog box that indicates termination of the command appears, check the value
that was output to the following file.
#
1
File
root-directory-of-the-OS-startup-drive\hcmdsrtn.enf
If the value is 2, restart the OS, and then re-execute the command described in step (1) c) in section
3-b.5.2.7.
If the value is not 2, or if the value is still 2 after re-execution, restart the OS, and then go to
section 3-b.5.2.8.
(2) Delete the registry keys.
a)
Start the registry editor and make sure that the following registry keys do not exist.
If these registry keys exist, delete them manually.
#
Registry Key
(When x86 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\HiCommand Base
2
(When x64 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\
HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3
HBaseStgMgmtComService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
4
HBaseStgMgmtWebService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
5
HBaseStorageMgmtWebSSOService
234
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
6
HiRDBClusterService_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
7
HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
8
Application\HBase Storage Mgmt Log
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
9
Application\HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
10
Application\HitachiWebServer
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
11
{1345FCD1-713E-4449-8F76-3F6503941040}
Note: If other Hitachi Storage Command Suite products have been installed, the registry key
name Hitachi might be displayed as HITACHI (in all upper-case letters).
(3) Delete the temporary directories for installation.
If the following directories exist, delete them manually.
#
Directory
%temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
%SystemDrive%\_HDBInstallerTemp
3-b.5.2.8
File name
Hitachi-Tuning-Manager-installation-directory\inst\db_area.properties
Hitachi-Tuning-Manager-installation-directory\inst\db_area_6.properties
b) In these files, check the values of the properties indicated below, which indicate the
database file directories. Note that the db_areapath2 property might not be specified in the
file.
#
Property Name
db_areapath1
db_areapath2
235
c) Delete the directories specified as the values of the db_areapath1 and db_areapath2
properties.
If the directories do not exist, go to step (2) in section 3-b.5.2.8.
(2) Delete the database files used by Hitachi Storage Command Suite Common Component.
Delete the directory you wrote down in step (1) of section 3-b.5.2.3.
If the directory does not exist, go to section 3-b.5.2.9.
If no file existed in step (1) a) of section 3-b.5.2.3, go to section 3-b.5.2.9.
3-b.5.2.9
Directory
<Installation directory>
%ProgramFiles%\InstallShield Installation Information\
2
{89331AB6-2E76-4986-9458-54795EF060A0}
%ProgramFiles%\InstallShield Installation Information\
3
{639938A4-41F1-4643-B5E9-05B1CAC6DA21}
%ProgramFiles%\InstallShield Installation Information\
4
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
%ProgramFiles%\InstallShield Installation Information\
5
{1345FCD1-713E-4449-8F76-3F6503941040}
%ProgramFiles%\InstallShield Installation Information\
6
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
%ProgramFiles%\InstallShield Installation Information\
7
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
Registry Key
(When x86 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\
HiCommand Tuning Manager
1
(When x64 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\
HiCommand Tuning Manager
236
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
2
HiCommandTuningManager
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
3
Application\TuningManager
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
4
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
5
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
Note: If other Hitachi Storage Command Suite products have been installed, the registry key
name Hitachi might be displayed as HITACHI (in all upper-case letters).
3-b.5.2.10 Restarting the OS
a)
Make sure that the registry keys indicated below do not exist. If these registry keys exist,
delete them.
# Registry key to delete
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi
1 HiCommand Base
2 HiCommand Tuning Manager
3 HiRDBEmbeddedEdition_HD0
4 HTMPR
5 JP1PC
6 JP1PCMGR
7 JP1PCAGT0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
8 HBaseStgMgmtComService
9 HBaseStgMgmtWebService
10 HBaseStorageMgmtWebSSOService
11 HiCommandTuningManager
12 HiCommandTuningService
13 HiRDBClusterService_HD0
14 HiRDBEmbeddedEdition_HD0
15 JP1PCAGT_0A
16 JP1PCAGT_0S
17 JP1PCMGR_PC
18 JP1PCMGR_PE
19 JP1PCMGR_PH
20 JP1PCMGR_PM
21 JP1PCMGR_PN
22 JP1PCMGR_PP
23 JP1PCMGR_PS
24 JP1PCMGR_PT
25 PerformanceReporter
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application
26 HBase Storage Mgmt Log
27 HiRDBEmbeddedEdition_HD0
28 HitachiWebServer
29 HTM-Tuning Service
30 PFM
31 PFM-HealthCheck
32 TuningManager
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
33 {89331AB6-2E76-4986-9458-54795EF060A0}
34 {639938A4-41F1-4643-B5E9-05B1CAC6DA21}
237
35
36
37
38
39
b)
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
{1345FCD1-713E-4449-8F76-3F6503941040}
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
Open a command prompt, and then move to the directory indicated below.
If this directory does not exist, go to section 3-b.5.2.12.
#
1
2.
Directory
Hitachi Storage Command-Suite-Common-Component-installation-directory\bin
#
1
Command line
hcmdsintg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ"
represents a one-byte space)
If TuningManager is included in the output results, as shown in the output example below, go
to the next step. If TuningManager is not included, go to section 3-b.5.2.12.
Output example
Command line
hcmdsintg
/delete
/type
"INTERNALHRXJIHVZ"
TuningManager
/user
"htnmrepuser"
( represents a one-byte space)
238
/pass
d) Execute the command indicated below. Make sure that TuningManager is not included in
the output results.
#
1
Command line
hcmdsintg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ"
represents a one-byte space)
3-c
This content was deleted, because it pertained to version 5 or earlier. To see this content, see the
documents for versions earlier than version 8.
3-d Deleting Tuning Manager server for Solaris (In Ver.6.0.0 to earlier than 8.0.0)
3-d.1
Purpose
This appendix provides an overview of deleting Tuning Manager server for Solaris, and describes
the following procedures (which are not disclosed to users):
- Procedure for deleting Tuning Manager server without deleting Agent
- Procedure for forcibly deleting the Tuning Manager server manually
3-d.2
Applicable Versions
3-d.3
Figure 3-d.3-1 shows an overview of the process for deleting Tuning Manager server.
239
START
No
Yes
Yes
Forcibly
Stopping services.
Was the
uninstallation
successful?
No
Deleting
Is the
/tmp/hcmdsrtn.enf
value 0?
No
Yes
END
Restarting the OS
Deleting packages
Restarting the OS
Figure 3-d.3-1 The flow of the deletion of the Tuning Manager server
240
Notes:
-
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, use the deletion procedure described in 3-d.4. Do not use the forced
deletion procedure described in 3-d.5. If you do, all Hitachi Storage Command Suite products,
including Agent, will no longer start.
Only perform the forced deletion procedure described in section 3-d.5 if you cannot perform a
normal uninstallation.
Before you forcibly delete Tuning Manager server, make sure that Hitachi Storage Command
Suite family of products other than Tuning Manager server have not been installed. If such
products have been installed, uninstall them before forcibly deleting Tuning Manager server.
For details about how to uninstall a HiCommand product, see the maintenance manual or other
manuals for the product.
The deletion procedure described in this document does not change the settings of Hitachi
Storage Command Suite family of products (including Agents), such as HiCommand Device
Manager, that are installed on hosts other than the host on which Tuning Manager server is
installed. To change the settings of such products, see the maintenance manual or other manuals
for the products.
3-d.4
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, uninstall Tuning Manager server as described below.
Value to specify
$CM_NOUNINST
Output results
Explanation
m_ss}.trc
uninstalled.
2 HTMPR_UNINST_LO
G_{MM-DD-YYYY_h
HTM - Performance
Reporter uninstallation
h_mm_ss}.trc
log
241
3-d.5
3-d.5.1
Stopping Services
Command
./hcmdssrv status
Output results
KAPM06441-I The HiRDB service has already stopped.
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Web Service
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Common Service
KAPM05009-I Already stopped service. service-name=HiCommand Suite TuningManager
KAPM05009-I Already stopped service. service-name=HiCommand Suite TuningService
KAPM05009-I Already stopped service. service-name=HiCommand Performance Reporter
If the service statuses are not the same as those indicated in the above output results 10 minutes
after performing step (1), restart the OS, and then perform step (1) again. If the services still
have not stopped, go to section 3-d.5.2.
Depending on the status after uninstallation, some services might no longer exist. In this case,
make sure that all the displayed services have stopped.
3-d.5.2
(1) Write down the directory name specified for the initpath property in the file indicated below.
If this file does not exist, go to step (2).
#
File name
Property name
/opt/HiCommand/Base/conf/hcmdsdbinit.ini
initpath
242
File to copy
/var/opt/HiCommand/Base/tmp/HBuninst.sh
3
4
3-d.5.3
Command
cd /opt/HiCommand/Base/bin/
./hcmdscancel PerformanceReporter
./hcmdscancel TuningManager
Command
cd <directory-to-which-HBuninst.sh-has-been-copied>
./HBuninst.sh /X
The message indicated under "Output result 2" is output. Enter Yes for this message
Output result 2
KAPM04316-W Are you sure you want to delete all of the files? Yes/No:
File
/tmp/hcmdsrtn.enf
243
Regardless of the value, if a service was running during command execution, restart the OS,
and then perform step (2) again. Next, perform the following procedure:
(a) If the value is 0, restart the OS, and then go to section 3-d.5.7.
(b) If the value is 1, restart the OS, and then perform step (2) again.
The operation you perform next differs depending on the result of performing step (2):
If the value is 0, restart the OS again, and then go to section 3-d.5.7.
If the value is not 0, go to section 3-d.5.4.
(c) If the value is 2, the environment is invalid. Revise the service status and other items,
and then perform step (2) again.
The operation you perform next differs depending on the result of performing step
(2):
If the value is 0, go to (a).
If the value is 1, go to (b).
If the value is still 2, go to section 3-d.5.4.
3-d.5.4
File
/etc/init.d/HiRDB_E.opt.HiCommand.Base.HDB
/etc/rc0.d/K090HiRDB_E.opt.HiCommand.Base.HDB
/etc/rc1.d/K090HiRDB_E.opt.HiCommand.Base.HDB
/etc/rc2.d/S91HiRDB_E.opt.HiCommand.Base.HDB
/etc/rc3.d/S91HiRDB_E.opt.HiCommand.Base.HDB
3-d.5.5
Restarting the OS
244
3-d.5.6
Environment
Value
variable name
1
PDDIR
/opt/HiCommand/Base/HDB
PDCONFPATH
/opt/HiCommand/Base/HDB/conf
LD_LIBRARY_PATH /opt/HiCommand/Base/HDB/lib
Shell
1 bash
source /opt/HiCommand/Base/HDB/bin/pduxenv
2 sh
PDDIR=/opt/HiCommand/Base/HDB
PDCONFPATH=/opt/HiCommand/Base/HDB/conf
LD_LIBRARY_PATH=/opt/HiCommand/Base/HDB/lib
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
3 csh/tcsh
4 Other shells
Command
/opt/HiCommand/Base/HDB/bin/pdstop f
(3) Execute the following command to confirm that a pdprcd process is running.
#
Command
ps ef |grep pdprcd
Command
kill 9 <pdprcd-process-number>
Note: You can use the ps command to check the process number (PID) of pdprcd.
245
3-d.5.7
If there are no such files, proceed to (2). Note that these files
File Name
/opt/HiCommand/TuningManager/inst/db_area.properties
/opt/HiCommand/TuningManager/inst/db_area_6.properties
(b) In these files, check the values of the properties indicated below, which indicate the
database file directories. Note that the db_areapath2 property might not be specified in the
file.
#
File Name
db_areapath1
db_areapath2
(c) Delete the directories indicated by the properties db_areapath1 and db_areapath2. If there
are no such directories, proceed to (2).
3-d.5.8
Deleting Packages
Command
pkgrm HTMCD1
If the pkgrm command fails, delete the directory indicated below. If the package has been
uninstalled and the directory no longer exists, go to the next step.
#
Directory
/var/sadm/pkg/HTMCD1
Command
pkgrm HTMCD2
If the pkgrm command fails, delete the directory indicated below. If the package has been
246
Directory
/var/sadm/pkg/HTMCD2
Command
pkgrm HTMClmgr
If the pkgrm command fails, delete the directory and files indicated below. If the package has been
uninstalled and the directory and files no longer exist, go to the next step.
#
Directory
/var/sadm/pkg/HTMClmgr
Files
/etc/init.d/jp1_pc
/etc/rc0.d/K01_JP1_10_PC
/etc/rc2.d/S99_JP1_90_PC
Command
pkgrm HTMPR
If the pkgrm command fails, delete the directory indicated below. If the package has been
uninstalled and the directory no longer exists, go to the next step.
#
Directory
/var/sadm/pkg/HTMPR
Command
pkgrm HTMTsvc
If the pkgrm command fails, delete the directory indicated below. If the package has been
uninstalled and the directory no longer exists, go to the next step.
#
Directory
/var/sadm/pkg/HTMTsvc
247
Command
pkgrm HBASE
If the pkgrm command fails, delete the directory indicated below. If the package has been
uninstalled and the directory no longer exists, go to the next step.
#
Directory
/var/sadm/pkg/HBASE
3-d.5.9
Directory
/opt/HiCommand
/var/opt/HiCommand
/opt/jp1pc
jp1pcstatsvr 22350/tcp
jp1pcvsvr 22286/tcp
jp1pcovsvr 22292/tcp
Execute the following commands to delete installed information, and then terminate the
commands.
#
Command
/etc/hitachi_setup
/etc/hitachi_x64setup
JP1/PFM - Manager
Use the following command to check the number of products that have been installed.
#
Command
/etc/.hitachi/bin/SHOWPP
248
If the command displays TOTAL: 0 products, delete the following directory and files.
#
Directory
/etc/.hitachi
Files
/etc/hitachi_start
/etc/hitachi_setup
/etc/hitachi_x64setup
d) Execute the command indicated below. Make sure that TuningManager is not included in
the output results.
#
1
Command line
hcmdsintg -print -user "htnmrepuser" -pass " INTERNAL HRXJIHVZ"
3-e Force uninstall of the Tuning Manager agents for Windows (In Ver.6.0.0 to earlier
than 8.0.0)
3-e.1
Purpose
This is the procedure for how to delete the agents (Windows) of Hitachi Tuning Manager in force.
3-e.2
Support version
All of the following agents of HiCommand Tuning Manager for Windows 6.0.0-00 to earlier than
8.0.0-00.
#
Agent
Version
OS
RAID Agent
Windows
Windows
Switch Agent
Windows
NAS Agent
Windows
Oracle Agent
Windows
SQL Agent
Windows
information is still remained which does not affect the re-install of the agents.
250
3-e.4
Figure 3-e.4-1 shows the flow of the deletion of the agent and the flow of re-install the agent.
Start
No
of the agent
Yes
Stop the agent related service
Reboot the OS
Both conditions
in (*1) met?
No
Yes
Use the htnmagtregclean
command to delete the registry
Reboot the OS
End
Figure 3-e.4-1 The flow of the deletion of the agent and re-install the agent
251
3-e.5
Uninstall the agent by following with the procedure described in the manual HiCommand
Tuning Manager Installation Guide. If the attempt for uninstalling the agent successfully ends,
then following window of the completion of uninstall is shown.
3-e.6
3-e.6.1
(1) Change the type of the start up of the agent related service
a) Start the service applet
b) Change the type of the start up of the following agent related services into [manual].
[Note] Some of the following service may not be shown depending on the installation
configuration or the uninstall status described in section 3-e.4.
252
PFM - Correlator
10
11
12
13
14
15
The characters xxxx indicates the type of the agent, the characters yyyy indicates the instance
name of the agent when the agent is multi instance type agent. Following table shows the type of
agent and single/multi instance agent information.
253
Agent
RAID Agent
RAID
Multi Instance
RAID Map
Single Instance
Windows
Single Instance
MSExchange
Single Instance
Switch Agent
SANSwitch
Multi Instance
NAS Agent
NAS
Multi Instance
Oracle Agent
Oracle
Multi Instance
SQL Agent
Multi Instance
[*1] Agent for Server System consists of 3 agents, RAID Map/Windows/Exchange agent.
3-e.6.2
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC\PathName
<Windows (x64)>
#
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC\
PathName
(c)The value of the entry Path00 of the registry key in (b) is the installation directory of the
agent.
#
1
3-e.6.3
Command
rd /S /Q <Agent Installation Directory>
Deleting the registry keys (by using the htnmagtregclean command (version 1.0.0) )
The following are the prerequisites for using the htnmagtregclean command.
#
Supported OS
Architecture
Note
x86
Including R2.
x64
Including R2.
IPF
x86
x64
Including R2.
IPF
Agent
Version
RAID Agent
Switch Agent
NAS Agent
Oracle Agent
SQL Agent
255
Notes
Only users with administrator privileges can use the htnmagtregclean command. If a user
without administrator privileges attempts to execute the command, the registry keys might not
be deleted, and records might not be output to the log file.
Before executing the htnmagtregclean command, all agent-related services must be stopped. If
an agent-related service is running and an attempt is made to execute the command, the
registry keys might not be deleted.
The results of executing the htnmagtregclean command are output to a log file
(htnmagtregclean.log), which is directly under the system drive. Make sure that the available
space on the system drive is not less than the size indicated below. If there is not enough
available space, records might not be output to the log file.
< Output log file size >
(10+n)KB
If there is already a log file that contains information, new entries are added to the existing
file. For this reason, do not make the log file read-only. If the file is read-only, no log data will
be output to the file.
4
If the User Account Control (UAC) function is being used in Windows Server 2008, use an
elevated command prompt that has administrator privileges to execute the htnmagtregclean
command. Move the mouse pointer over the command prompt icon, and then right-click it. A
context menu appears. From this menu, select Run as administrator to start an elevated
command prompt that has administrator privileges. If you attempt to use an unelevated
command prompt to execute the htnmagtregclean command, the registry keys might not be
deleted.
After you execute the htnmagtregclean command, delete the log file.
During execution, do not cancel the htnmagtregclean command by Windows operations such
as pressing [Ctrl] + [C] (however, interrupting the command by responding to messages is
permitted). If you cancel the command, you must re-execute it.
256
The htnmagtregclean command can be used to delete the following registry keys:
<Windows (x86) or Windows (IPF)>
#
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTP
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTx
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
<Windows (x64)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
(1) Start a command prompt. If the UAC function is being used in Windows Server 2008, start an
elevated command prompt that has administrator privileges.
Command
htnmagtregclean
To continue, enter [y] or [Y]. To cancel the command, enter [n] or [N].
(4) Check the end code that appears in the command prompt in response to the htnmagtregclean
command.
End code
Processing Result
Log File
%SystemDrive%\htnmagtregclean.log
The reasons an attempt to delete one or more registry keys fails, and the corresponding
actions to be taken, are described in the following table.
#
Cause
user
Action
without
privileges attempted to execute the group, and then re-execute the htnmagtregclean
htnmagtregclean command.
2
command.
In the access permission settings for a Open the registry editor, and then disable the Deny
registry key, Deny has been specified setting for Delete Permission in the access
the
OS,
and
then
re-execute
the
htnmagtregclean command.
4
If the UAC function is being used in Move the mouse pointer over the command prompt
Windows Server 2008, no attempt is icon, and then right-click it. A context menu appears.
made to use an elevated command From this menu, select Run as administrator to
prompt
privileges
that
has
to
htnmagtregclean command.
(5) After using the htnmagtregclean command to delete the registry keys, delete the log file.
258
Log File
%SystemDrive%\htnmagtregclean.log
01/06/2010
12:01:38.33
(I)
The
following
registry
key
exists:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_WS_Bro1
Wed 01/06/2010 12:01:38.33 (I) The following registry key was removed successfully:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_WS_Bro1
01/06/2010
12:01:38.33
(I)
The
following
registry
key
exists:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_WA_Bro1
Wed 01/06/2010 12:01:38.33 (W) An attempt to remove the following registry key has failed:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_WA_Bro1
259
3-e.6.4
(1) Check whether following registry keys exist or nor by using registry editor, and if exist, delete
them by manually.
<Windows (x86) or Windows (IPF)>
#
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTP
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTx
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
<Windows (x64)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
3-e.6.5
Reboot the OS
260
3-f Force uninstall of the Tuning Manager agents for UNIX (In Ver.6.0.0 to earlier than
8.0.0)
3-f.1
Purpose
This is the procedure for how to delete the agents for UNIX (Solaris (SPARC)/Solaris
(x64)/HP-UX/AIX/Linux) of Hitachi Tuning Manager in force.
3-f.2
Support version
All of the following agents of HiCommand Tuning Manager for Unix 6.0.0-00 to earlier than
8.0.0-00
#
Agent
Version
OS
RAID Agent
6.0.0-00 to 7.0 *1
HP-UX/AIX/Linux
Switch Agent
6.0.0-00 to 6.1 *1
Solaris (SPARC)/HP-UX/AIX
6.2 *1
Solaris (SPARC)
6.3.0-00 to 7.0 *1
NAS Agent
6.0.0-00 to 6.2 *1
Solaris (SPARC)/HP-UX/AIX
Oracle Agent
DB2 Agent
EAP Agent
information is still remained which does not affect the re-install of the agents.
(*1) Including its bug fix version
261
3-f.4
Figure 3-f.4-1 shows the flow of the deletion of the agent and the flow of re-install the agent.
Start
Uninstaller
No
Normally End
Yes
Delete the file/directory
Reboot the OS
End
Figure 3-f.4-1 The flow of the deletion of the agent and re-install the agent
262
3-f.5
- In Ver.7
Hitachi Command Suite Tuning Manager Software Installation Guide
If the attempt for uninstalling the agent successfully ends, then following message that indicates
the completion of uninstall is shown.
(Example) The case of RAID Agent
Mon Sep 28 12:00:00 GMT 2007
Done uninstalling HiCommand Tuning Manager - Agent for RAID
If the attempt for uninstall the agent does not successfully end, go to the chapter 3-f.6 to delete the
agent installation environment in force.
3-f.6
3-f.6.1
Command
1
cd /opt/jp1pc/tools
./jpcstop all
Command
rm -rf /opt/jp1pc/jpc_start
For AIX:
rmitab jp1pc
For SUSE Linux:
chkconfig jp1_pc off
Command
For Solaris:
cd /opt/HiCommand/Base/bin
For Linux:
cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
3-f.6.2
./hcmdssrv -stop
File
(b) Linux
#
File
Command
1
3-f.6.3
rm -rf /opt/jp1pc
Reboot the OS
Reboot the OS.
264
3-g
Deleting Tuning Manager server for Linux (In Ver.7.1.0 to earlier than 8.0.0)
3-g.1
Purpose
This appendix provides an overview of deleting Tuning Manager server for Linux, and describes the
following procedures (which are not disclosed to users):
- Procedure for deleting Tuning Manager server without deleting Agent
- Procedure for forcibly deleting the Tuning Manager server manually
3-g.2
Applicable Versions
3-g.3
Figure 3-g.3-1 shows an overview of the process for deleting Tuning Manager server.
265
START
No
Yes
Yes
Forcibly
Stopping services.
Was the
uninstallation
successful?
No
Deleting
Is the
/tmp/hcmdsrtn.enf
value 0?
No
Yes
END
Restarting the OS
Deleting packages
Restarting the OS
Figure 3-g.3-1 The flow of the deletion of the Tuning Manager server
266
Notes:
-
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, use the deletion procedure described in 3-g.4. Do not use the forced
deletion procedure described in 3-g.5. If you do, all Hitachi Storage Command Suite products,
including Agent, will no longer start.
Only perform the forced deletion procedure described in section 3-g.5 if you cannot perform a
normal uninstallation.
Before you forcibly delete Tuning Manager server, make sure that Hitachi Storage Command
Suite family of products other than Tuning Manager server have not been installed. If such
products have been installed, uninstall them before forcibly deleting Tuning Manager server.
For details about how to uninstall a HiCommand product, see the maintenance manual or other
manuals for the product.
The deletion procedure described in this document does not change the settings of Hitachi
Storage Command Suite family of products (including Agents), such as HiCommand Device
Manager, that are installed on hosts other than the host on which Tuning Manager server is
installed. To change the settings of such products, see the maintenance manual or other manuals
for the products.
3-g.4
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, uninstall Tuning Manager server as described below.
Value to specify
$CM_NOUNINST
# File name
Output results
Explanation
m_ss}.trc
uninstalled.
2 HTMPR_UNINST_LO
G_{MM-DD-YYYY_h
HTM - Performance
Reporter uninstallation
267
h_mm_ss}.trc
log
3-g.5
3-g.5.1
Stopping Services
Command
./hcmdssrv status
Output results
KAPM06441-I The HiRDB service has already stopped.
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Web Service
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Common Service
KAPM05009-I Already stopped service. service-name=HiCommand Suite TuningManager
KAPM05009-I Already stopped service. service-name=HiCommand Performance Reporter
If the service statuses are not the same as those indicated in the above output results 10 minutes
after performing step (1), restart the OS, and then perform step (1) again. If the services still
have not stopped, go to section 3-g.5.2.
Depending on the status after uninstallation, some services might no longer exist. In this case,
make sure that all the displayed services have stopped.
268
3-g.5.2
(1) Write down the directory name specified for the initpath property in the file indicated below.
If this file does not exist, go to step (2).
#
File name
Property
name
<Hitachi-Command-Suite-Common-Component-Installation-directory>/conf/hcmdsdbinit.ini
initpath
File to copy
/var<Hitachi-Command-Suite-Common-Component-Installation-directory>/tmp/HBuninst.sh
<Hitachi-Command-Suite-Common-Component-Installation-directory>
(including
subdirectories)
3
/var<Hitachi-Command-Suite-Common-Component-Installation-directory> (including
subdirectories)
3-g.5.3
Command
cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin/
./hcmdscancel PerformanceReporter
./hcmdscancel TuningManager
Command
cd <directory-to-which-HBuninst.sh-has-been-copied>
./HBuninst.sh /X
Output result 1
KAPM04315-W All the files for HBASE will now be deleted. Is this OK? Yes/No:
The message indicated under "Output result 2" is output. Enter Yes for this message
Output result 2
KAPM04316-W Are you sure you want to delete all of the files? Yes/No:
File
/tmp/hcmdsrtn.enf
Regardless of the value, if a service was running during command execution, restart the OS,
and then perform step (2) again. Next, perform the following procedure:
(a) If the value is 0, restart the OS, and then go to section 3-g.5.7.
(b) If the value is 1, restart the OS, and then perform step (2) again.
The operation you perform next differs depending on the result of performing step (2):
If the value is 0, restart the OS again, and then go to section 3-g.5.7.
If the value is not 0, go to section 3-g.5.4.
(c) If the value is 2, the environment is invalid. Revise the service status and other items,
and then perform step (2) again.
The operation you perform next differs depending on the result of performing step
(2):
If the value is 0, go to (a).
If the value is 1, go to (b).
If the value is still 2, go to section 3-g.5.4.
3-g.5.4
File
/etc/init.d/HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
/etc/rc0.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
270
10
/etc/rc1.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
11
/etc/rc2.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
12
/etc/rc3.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
13
/etc/rc5.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
14
/etc/rc6.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
15
16
3-g.5.5
Restarting the OS
3-g.5.6
Environment
Value
variable name
1
PDDIR
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
PDCONFPATH
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/conf
LD_LIBRARY_PATH
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib
Shell
271
bash
source <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/
pduxenv
sh
PDDIR=<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
PDCONFPATH=<Hitachi-Command-Suite-Common-Component-Installation-directory>/
HDB/conf
LD_LIBRARY_PATH=<Hitachi-Command-Suite-Common-Component-Installation-dire
ctory>/HDB/lib
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
csh/tcsh
Other shells
Command
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdstop f
(3) Execute the following command to confirm that a pdprcd process is running.
#
Command
ps ef |grep pdprcd
(4) If
the
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib/servers/pdprcd
Command
kill 9 <pdprcd-process-number>
Note: You can use the ps command to check the process number (PID) of pdprcd.
3-g.5.7
If there are no such files, proceed to (2). Note that these files
File Name
<TuningManager-Installation-directory>/inst/db_area.properties
272
<TuningManager-Installation-directory>/inst/db_area_6.properties
(b) In these files, check the values of the properties indicated below, which indicate the
database file directories. Note that the db_areapath2 property might not be specified in the
file.
#
File Name
db_areapath1
db_areapath2
(c) Delete the directories indicated by the properties db_areapath1 and db_areapath2. If there
are no such directories, proceed to (2).
3-g.5.8
Deleting Packages
Command
rpm -e HTNM
Command
rpm e HTMPR
3-g.5.9
Directory
<TuningManager-Installation-directory>
/var<TuningManager-Installation-directory>
<Hitachi-Command-Suite-Common-Component-Installation-directory>
/var<Hitachi-Command-Suite-Common-Component-Installation-directory>
/opt/jp1pc
/etc/.hitachi/HBase
/etc/.hitachi/HTNM
Entry to delete
jp1pcnsvr 22285/tcp
jp1pcstatsvr 22350/tcp
jp1pcvsvr 22286/tcp
jp1pcovsvr 22292/tcp
Execute the following commands to delete installed information, and then terminate the
commands.
#
Command
/etc/hitachi_setup
JP1/PFM - Manager
Use the following command to check the number of products that have been installed.
#
Command
/etc/.hitachi/bin/SHOWPP
If the command displays TOTAL: 0 products, delete the following directory and files.
If the execution result of the command is not zero, Agent might remain in any hosts on which
Tuning Manager has been installed.
If the instance of Agent is not necessary, execute "/etc/hitachi_setup" again to uninstall the
Agent. If "/etc/hitachi_setup" fails to uninstall the Agent, perform step 3-f.
To use Agent after making forcible deletion of Tuning Manager, perform step 3-g.5.10.
#
Directory
/etc/.hitachi
Files
/etc/hitachi_start
/etc/hitachi_setup
275
3-h
3-h.1
Purpose
This appendix provides an overview of deleting Tuning Manager server for Windows, and describes
the following procedures (which are not disclosed to users):
- Procedure for deleting Tuning Manager server without deleting Agent
- Procedure for forcibly deleting the Tuning Manager server manually
When performing a forced uninstallation in Windows, you can use the Hitachi Command Suite
cleanup tool. For details about the Hitachi Command Suite cleanup tool, see the section "A-20
Hitachi Command Suite cleanup tool" of "Hitachi Command Suite Software Troubleshooting
Guide".
3-h.2
Applicable Versions
3-h.3
Figure 3-h.3-1 shows an overview of the process for deleting Tuning Manager server.
Start
Forcibly Deleting Tuning Manager server
Do you want to perform
an uninstallation that leaves
Agents?
NO
YES
NO
Was the uninstallation successful?
YES
Normal uninstallation procedure
NO
YES
YES
NO
End
End
End
276
Figure 3-h.3-1 The flow of the deletion of the Tuning Manager server
Notes:
-
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, use the deletion procedure described in 3-h.4. Do not use the forced
deletion procedure described in 3-h.5. If you do, all Hitachi Command Suite (incluFile Services
Manager or Storage Navigator Modular2) products, including Agent, will no longer start.
Only perform the forced deletion procedure described in section 3-h.5 if you cannot perform a
normal uninstallation.
Before you forcibly delete Tuning Manager server, make sure that Hitachi Command Suite
family (including Hitachi File Services Manager and Hitachi Storage Navigator Modular 2) of
products other than Tuning Manager server have not been installed. If such products have been
installed, uninstall them before forcibly deleting Tuning Manager server. For details about how
to uninstall a Hitachi Command Suite product, see the maintenance manual or other manuals
for the product.
Because the forced deletion procedure edits the registry, special care is required.
The deletion procedure described in this document does not change the settings of Hitachi
Command Suite family (including Agents, Hitachi File Services Manager and Hitachi Storage
Navigator Modular 2) of products (including Agents), such as HiCommand Device Manager,
that are installed on hosts other than the host on which Tuning Manager server is installed. To
change the settings of such products, see the maintenance manual or other manuals for the
products.
3-h.4
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, uninstall Tuning Manager server as described below.
(1) Environment variable specification
Define the following environment variable.
#
1
Value to set
1
Figure 3-h.4-1: Window that appears when Tuning Manager server is successfully uninstalled
(3) Environment variable specification.
Make sure that no value has been specified for the following environment variable.
#
1
Note: If an error occurs during the deletion procedure in 3-h.4, integrity of the environment will
be lost. If such an error occurs, you might need to completely delete the environment by using
the forced deletion procedure in 3-h.5.
Note: After performing the deletion procedure described in section 3-h.4, do not install Hitachi
Command Suite family (including Hitachi File Services Manager and Hitachi Storage
Navigator Modular 2) of products until you have re-installed Tuning Manager server.
3-h.5
In 8.0.0 or later
2.0.0-00
Notes:
278
If an upgrade installation from version 7 or earlier of the Tuning Manager server fails, you might
need to forcibly delete the Tuning Manager server. If you need to forcibly delete the Tuning Manager
server, depending on the reason the upgrade installation failed, you need to delete the components,
registry entries, directories, and files of both the old (version 7 or earlier) and new (version 8 or
later) versions.
In the relevant procedure, in sections for which operations for version 7 and for version 8 differ,
notes to that effect are given. When you use the procedure for forcibly deleting the Tuning Manager
server, do not overlook these notes. When performing operations for the old version (version 7 or
earlier), replace the relevant instructions, which are for the new version, with the instructions
described below, which are for the old version. Note that if the operations described relate to
directories, files, registry entries, or other items that do not exist in the environment of the old
version (version 7 or earlier), you do not need to perform those operations.
the
above
text
with
the
following
text:
%SystemDrive%\Program
Files\HiCommand\Base\bin\hcmds***
279
Note that the underlined paths in the above are an example of if the product was installed in the default
installation directory during a new installation. If the installation directory was changed from the default, use
the actual installation directory regardless of the environment.
3-h.5.1
3-h.5.1.1
Terms
The following terms are used in this section.
Terms
Directory
Hitachi Command
%SystemDrive%\Program Files\HiCommand\Base64
Suite-Common-Component-installation-d
irectory
Hitachi-Tuning-Manager-installation-dire
2
ctory
Collection Manager installation-directory
%SystemDrive%\Program
Files
(x86)
3
\HiCommand\TuningManager
Note1: Unless you specify other directories during installation, the above directories are
used by default.
Note2: In a 64-bit edition of Windows, if Tuning Manager Server (version 7 or earlier) is
upgraded to version 8 or later, the default installation directory for Hitachi Command Suite
Common Component and Tuning Manager Server changes as follows:
Before upgrading (v7 or earlier): %SystemDrive%\Program Files (x86) \HiCommand
After upgrading (v8 or later): %SystemDrive%\Program Files \HiCommand
Note 3: If the installation path was changed from the default during a new installation, the
underlined path in the above also changes to the 5new installation path regardless of the
environment. In such a case, when the product is upgraded from version 7 to 8, the
installation directory does not change.
3-h.5.1.2
a) Open a command prompt, and then move to the directory indicated below.
280
Directory
Command
hcmds64srv /stop
c) Execute the following command and make sure that stopped is displayed for the displayed
services, as shown in the output example below.
#
Command
hcmds64srv /status
Note: Depending on the uninstallation status, some services might not be displayed.
Note: If stopped is still not displayed for hcmds64srv /status 10 minutes after executing
hcmds64srv /stop, go to step (1) d) in section 3-h.5.1.2.
d) Move to the directory indicated below.
If the directory does not exist, go to step (2) in section 3-h.5.1.2.
#
Directory
Collection-Manager-installation-directory\jp1pc\tools
Command
281
jpcstop all
If the message KAVE05000-E The specified service is not running is displayed, the service is
not running, so go to the next step.
Output example
KAVE06008-I The service will now stop. (service=Action Handler)
KAVE06008-I The service will now stop. (service= Agent for HealthCheck)
KAVE06008-I The service will now stop. (service= Agent Store for HealthCheck)
KAVE06008-I The service will now stop. (service= View Server)
KAVE06008-I The service will now stop. (service=Trap Generator)
KAVE06008-I The service will now stop. (service=Correlator)
KAVE06008-I The service will now stop. (service=Master Store)
KAVE06008-I The service will now stop. (service=Master Manager)
KAVE06008-I The service will now stop. (service=Name Server)
KAVE06008-I The service will now stop. (service=Status Server)
Note: Depending on the uninstallation status, some services might not be displayed.
f)
Execute the command indicated below and make sure that Inactive* is displayed for the
displayed services, as shown in the output example below.
If the jpcctrl command does not exist, go to step (2) in section 3-h.5.1.2.
Even if Inactive* is not displayed (and another string, such as Active, is displayed instead),
Command
jpcctrl list *
If the message KAVE05024-E The specified service is not registered. is displayed, the service
is not running, so go to the next step.
Example of the output
Host Name
ServiceID
Service Name
PID
Port
Status
---------
---------
-------------
--------
--------
--------
XXXX
PN1001
Name Server
Inactive*
XXXX
PT1XXX
Status Server
Inactive*
XXXX
PCXXX
Trap Generator
Inactive*
XXXX
PM1001
Master Manager
Inactive*
XXXX
PS1001
Master Store
Inactive*
XXXX
PE1001
Correlator
Inactive*
XXXX
PP1XXX
View Server
Inactive*
XXXX
PH1XXX
Action Handler
Inactive*)
XXXX
OS1XXX
Agnet Store
Inactive*
XXXX
OA1XXX
Agent Collector
Inactive*
Note: Depending on the uninstallation status, some services might not be displayed.
Note: The asterisk (*) in Inactive* might not be displayed.
(2) Change the startup type for Hitachi Command Suite-related services.
282
HiRDB/ClusterService _HD1
HiRDB/EmbeddedEdition _HD1
10
11
12
13
14
PFM Correlator
15
16
17
18
In an environment in which an upgrade from version 7 or earlier has been performed, check
whether the services listed in the following table exist for the old version. If they do, make the
same changes for them.
#
HiRDB/ClusterService _HD0
HiRDB/EmbeddedEdition _HD0
3-h.5.1.3
In an environment in which an upgrade from version 7 or earlier has been performed, you also need
to perform the steps shown below in the old environment (version 7 or earlier). When you do so,
follow the text-replacement instructions described above.
(1) Check the directory that stores the database for Hitachi Command Suite Common Component.
a) Open the file indicated below.
If the file does not exist, go to step (2) in section 3-h.5.1.3.
#
File Name
b) Write down the value of the initpath property (the database file directory) specified in the
file.
(2) Delete the Tuning Manager server registration information.
a) Open a command prompt, and then move to the following directory.
If the directory does not exist, go to step (4) in section 3-h.5.1.3.
#
1
Directory
Hitachi Command Suite-Common-Component-installation-directory\bin
Command
Command
hcmdscancel TuningManager
File Name
%SystemDrive%\htmpruninst.rtn
3-h.5.1.4
File Name
Hitachi-Tuning-Manager-installation-directory\inst\cm_guid.dat
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
<Collection Manager-GUID>
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersio
n\Uninstall\<Collection Manager-GUID>
Command to execute
{UninstallString-command}/qn+
Note: If the uninstallation terminates successfully, the following dialog box indicating such
is displayed. Click OK to close the dialog box.
3-h.5.1.5
At present, in version 8 and later, you do not need to perform the procedures described in this
section. However, you might need to perform them in the future.
In an environment in which an upgrade from version 7 or earlier has been performed, make sure
that you perform these procedures.
(1) Execute the Tuning Service uninstaller.
a) Open a command prompt.
b) Start the registry editor and make sure that the registry key indicated below exists.
If this key does not exist, go to section 3-h.5.1.6.
#
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
286
3-h.5.1.6
In an environment in which an upgrade from version 7 or earlier has been performed, you also
need to perform the procedures described in this section for version 7. When you do so, replace the
registry information described in b) as follows.
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninst
all\{465EF71F-B608-4C33-9E19-D56DDCADC82A}
Command to execute
{UninstallString-value}/NOREBOOTNOFLAGOFF (: a single-byte space)
Note: Make sure that the Services applet is closed when executing the uninstaller.
e) Open the following file and make sure that the termination status has been output.
If the termination status has been output, the uninstallation has finished. Ignore any other output
values.
#
File Name
%SystemDrive%\htmpruninst.rtn
Note: If the file does not exist, the uninstallation is still in progress.
287
In an environment that satisfies any of the conditions listed below, two different instances of Hitachi
Command Suite Common Component (for 32bit OS and for 64bit OS) might be installed:
- Hitachi Command Suite version 7 or earlier is currently installed or was previously installed.
- File Services Manager is currently installed or was previously installed.
- Storage Navigator Modular 2 is currently installed or was previously installed.
(1) Forcibly deleting the 32-bit version of Hitachi Command Suite Common Component
a) Copy the command indicated below to the directory of the OS system drive. If the file does not
exist, go to step (2).
#
1
File
Command line
HBuninst /X
d) After the dialog box that indicates termination of the command appears, check the
value that was output to the following file.
#
1
File
hcmdsrtn.enf
If the value is 2, restart the OS, and then re-execute the command described in step (1) c).
If the value is not 2, or if the value is still 2 after re-execution, restart the OS, and then go to step
288
(2).
(2) Forcibly deleting the 64-bit version of Hitachi Command Suite Common Component
a) Copy the command indicated below to the directory of the OS system drive. If the file does not
exist, go to section 3-h.5.1.8.
If you forcibly deleted the 32-bit version of Hitachi Command Suite Common Component, a
file with the same name might exist in the copy destination. In such a case, be sure to overwrite
the file.
#
File
To earlier than Ver.8.1
%SystemDrive%\Program Files\HiCommand\Base64\tmp\HBuninst.exe
Ver.8.1 or later
%SystemDrive%\Program Files\HiCommand\Base64\tmp\HB64uninst.exe
Note:
The above directory is the default installation directory of the 64-bit version of Hitachi
Command Suite Common Component.
b) Open a command prompt, and then move to the directory of the OS system drive.
c) Execute the command indicated below. Respond to all questions with Yes.
#
1
Command line
To earlier than Ver.8.1
HBuninst /X
Ver.8.1 or later
HB64uninst /X
d) After the dialog box that indicates termination of the command appears, check the value that
was output to the following file.
#
1
File
hcmds64rtn.enf
If the value is 2, restart the OS, and then re-execute the command described in step (2) c) in this
section.
If the value is not 2, or if the value is still 2 after re-execution, restart the OS, and then go to
section 3-h.5.1.8.
3-h.5.1.8
Do not use the Hitachi Command Suite registry deletion tool provided for version 7 or earlier to
delete registry for version 8 or later.
(1) Preparing to execute the registry deletion command
Before you execute the registry deletion command, confirm the following:
- Make sure that you have administrator privileges. If you do not have administrator privileges,
289
(4) Confirm the end code that appears after you execute the command.
Removal of the registry keys for HTnM Server has ended.
[End code: <end code>]
Press any key to continue.
(5) Refer to the end code and take the appropriate action.
If the end code is 1, open the file that is shown below and check the command execution results. If
you do not have administrator privileges, the log file might not be output.
290
File name
%SystemDrive%\htnmsvrregclean.log
End
Error
Cause
Action
Disable
Permission
code
1
Registry
deletion
failed.
the
Deny
of
setting
the access
in
Delete
permission
been locked.
3-h.5.1.9
command.
the command.
Reboot the OS
Reboot the OS
291
2
3
4
5
6
7
8
9
10
11
12
%SystemRoot%\SysWOW64\jpcaudit{vvrrss}.dll
%SystemRoot%\SysWOW64\jpccomm{vvrrss}.dll
%SystemRoot%\SysWOW64\jpccommhcc.dll
%SystemRoot%\SysWOW64\jpccoommhccjp.dll
%SystemRoot%\SysWOW64\jpcodbc.dll
%SystemRoot%\system32\htmjpccomm.dll
%SystemRoot%\system32\jpcaudit{vvrrss}.dll
%SystemRoot%\system32\jpccomm{vvrrss}.dll
%SystemRoot%\system32\jpccommhcc.dll
%SystemRoot%\system32\jpccoommhccjp.dll
%SystemRoot%\system32\jpcodbc.dll
Note: The {vvrrss} part in the file names is a string of alphanumeric characters that indicates
the DLL version number.
(2) Delete the component install temporary directories that are shared by Hitachi Command Suite.
If the following directories exist, delete them manually.
#
Directory
%temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
%SystemDrive%\_HDBInstallerTemp
File name
Hitachi-Tuning-Manager-installation-directory\inst\db_area.properties
Hitachi-Tuning-Manager-installation-directory\inst\db_area_6.properties
b) In these files, check the values of the properties indicated below, which indicate the
database file directories. Note that the db_areapath2 property might not be specified in the
file.
#
Property Name
db_areapath1
db_areapath2
c) Delete the directories specified as the values of the db_areapath1 and db_areapath2
properties.
If the directories do not exist, go to step (4) in section 3-h.5.1.10.
(4) Delete the database files used by Hitachi Command Suite Common Component.
292
In an environment in which an upgrade from version 7 or earlier has been performed, you also
need to perform the steps shown below in the old environment (version 7 or earlier)
Delete the directory you wrote down in step (1) of section 3-h.5.1.3.
If the directory does not exist, go to step (5) of section 3-h.5.1.10.
If no file existed in step (1) a) of section 3-h.5.1.3, go to step (5) of section 3-h.5.1.10.
(5) Delete the directories.
Make sure that the directories indicated below do not exist. If these directories exist, delete
them manually.
After confirming that the directories do not exist, go to section 3-h.5.1.11.
#
Directory
<Installation directory>
%ProgramFiles%\InstallShield Installation Information\
2
{89331AB6-2E76-4986-9458-54795EF060A0}
%ProgramFiles%\InstallShield Installation Information\
3
{639938A4-41F1-4643-B5E9-05B1CAC6DA21}
%ProgramFiles%\InstallShield Installation Information\
4
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
%ProgramFiles%\InstallShield Installation Information\
5
{1345FCD1-713E-4449-8F76-3F6503941040}
%ProgramFiles%\InstallShield Installation Information\
6
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
%ProgramFiles%\InstallShield Installation Information\
7
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
Directory
Hitachi Command Suite-Common-Component-installation-directory\bin
Command line
hcmds64intg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ"
represents a one-byte space)
If TuningManager is included in the output results, as shown in the output example below, go
to the next step. If TuningManager is not included, go to section 3-h.5.1.12.
Output example
Command line
hcmds64intg
/delete
/type
"INTERNALHRXJIHVZ"
TuningManager
/user
"htnmrepuser"
( represents a one-byte space)
/pass
d) Execute the command indicated below. Make sure that TuningManager is not included in
the output results.
#
1
Command line
hcmds64intg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ"
represents a one-byte space)
3-h.5.2
3-h.5.2.1
Terms
The following terms are used in this section.
Terms
Directory
Hitachi Command
%SystemDrive%\Program Files\HiCommand\Base64
Suite-Common-Component-installation-dir
ectory
Hitachi-Tuning-Manager-installation-direct
%SystemDrive%\Program
ory
\HiCommand\TuningManager
%SystemDrive%\Program
Files
2
Files
(x86)
3
\HiCommand\TuningManager
Note1: Unless you specify other directories during installation, the above directories are
used by default.
Note2: In a 64-bit edition of Windows, if Tuning Manager Server (version 7 or earlier) is
upgraded to version 8 or later, the default installation directory for Hitachi Command Suite
Common Component and Tuning Manager Server changes as follows:
Before upgrading (v7 or earlier): %SystemDrive%\Program Files (x86) \HiCommand
After upgrading (v8 or later): %SystemDrive%\Program Files \HiCommand
Note 3: If the installation path was changed from the default during a new installation, the
underlined path in the above also changes to the 5new installation path regardless of the
environment. In such a case, when the product is upgraded from version 7 to 8, the
installation directory does not change.
3-h.5.2.2
a) Open a command prompt, and then move to the directory indicated below.
If the directory does not exist, go to step (1) d) in section 3-h.5.2.2.
#
1
Directory
Hitachi Command Suite-Common-Component-installation-directory\bin
295
Command
hcmds64srv /stop
c) Execute the following command and make sure that stopped is displayed for the displayed
services, as shown in the output example below.
#
Command
hcmds64srv /status
Note: Depending on the uninstallation status, some services might not be displayed.
Note: If stopped is still not displayed for hcmds64srv /status 10 minutes after executing
hcmds64srv /stop, go to step (1) d) in section 3-h.5.2.2.
d) Move to the directory indicated below.
If the directory does not exist, go to step (2) in section 3-h.5.2.2.
#
Directory
Collection-Manager-installation-directory\jp1pc\tools
Command
jpcstop all
If the message KAVE05000-E The specified service is not running is displayed, the service is
not running, so go to the next step.
Output example
KAVE06008-I The service will now stop. (service=Action Handler)
KAVE06008-I The service will now stop. (service= Agent for HealthCheck)
296
KAVE06008-I The service will now stop. (service= Agent Store for HealthCheck)
KAVE06008-I The service will now stop. (service= View Server)
KAVE06008-I The service will now stop. (service=Trap Generator)
KAVE06008-I The service will now stop. (service=Correlator)
KAVE06008-I The service will now stop. (service=Master Store)
KAVE06008-I The service will now stop. (service=Master Manager)
KAVE06008-I The service will now stop. (service=Name Server)
KAVE06008-I The service will now stop. (service=Status Server)
Note: Depending on the uninstallation status, some services might not be displayed.
f)
Execute the command indicated below and make sure that Inactive* is displayed for the
displayed services, as shown in the output example below.
If the jpcctrl command does not exist, go to step (2) in section 3-h.5.2.2.
Even if Inactive* is not displayed (and another string, such as Active, is displayed instead),
Command
jpcctrl list *
If the message KAVE05024-E The specified service is not registered. is displayed, the service
is not running, so go to the next step.
Example of the output
Host Name
ServiceID
Service Name
PID
Port
Status
---------
---------
-------------
--------
--------
--------
XXXX
PN1001
Name Server
Inactive*
XXXX
PT1XXX
Status Server
Inactive*
XXXX
PCXXX
Trap Generator
Inactive*
XXXX
PM1001
Master Manager
Inactive*
XXXX
PS1001
Master Store
Inactive*
XXXX
PE1001
Correlator
Inactive*
XXXX
PP1XXX
View Server
Inactive*
XXXX
PH1XXX
Action Handler
Inactive*)
XXXX
OS1XXX
Agnet Store
Inactive*
XXXX
OA1XXX
Agent Collector
Inactive*
Note: Depending on the uninstallation status, some services might not be displayed.
Note: The asterisk (*) in Inactive* might not be displayed.
(2) Change the startup type for Hitachi Command Suite-related services.
a) Start the Services applet.
b) Change the startup type to Manual for all of the following Hitachi Command Suite-related
297
services. You can change the startup type from the Service Properties dialog box.
Note: Depending on the uninstallation status in section 3-h.4, some services might not be
displayed.
Note: The startup type will already be set to Manual for some services.
#
HiRDB/ClusterService _HD1
HiRDB/EmbeddedEdition _HD1
10
11
12
13
14
PFM Correlator
15
16
17
18
In an environment in which an upgrade from version 7 or earlier has been performed, check
whether the services listed in the following table exist for the old version. If they do, make the
same changes for them.
#
HiRDB/ClusterService _HD0
HiRDB/EmbeddedEdition _HD0
298
3-h.5.2.3
In an environment in which an upgrade from version 7 or earlier has been performed, you also need
to perform the steps shown below in the old environment (version 7 or earlier). When you do so,
follow the text-replacement instructions described above.
(1) Check the directory that stores the database for Hitachi Command Suite Common Component.
a) Open the file indicated below.
If the file does not exist, go to step (2) in section 3-h.5.2.3.
#
File Name
b) Write down the value of the initpath property (the database file directory) specified in the
file.
(2) Delete the Tuning Manager server registration information.
a) Open a command prompt, and then move to the following directory.
If the directory does not exist, go to step (4) in section 3-h.5.2.3.
#
1
Directory
Hitachi Command Suite-Common-Component-installation-directory\bin
Command
If any error message displayed except KAPM04118-E, wait about 10 seconds, then re-execute
the command. If the error messages still remain after re-execution three times, go to step (3) in
section 3-h.5.2.3.
Command
hcmdscancel TuningManager
File Name
%SystemDrive%\htmpruninst.rtn
3-h.5.2.4
File Name
Hitachi-Tuning-Manager-installation-directory\inst\cm_guid.dat
d) Use the registry editor to make sure that the registry key indicated below exists. If the 2
registry keys listed below exist, perform steps e) through g) twice.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
<Collection Manager-GUID>
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersio
n\Uninstall\<Collection Manager-GUID>
Paste the copied value into the command prompt, add the following option, and then
execute the command. The uninstallation will start.
Command to execute
{UninstallString-command}/qn+
Note: If the uninstallation terminates successfully, the following dialog box indicating such
is displayed. Click OK to close the dialog box.
#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCMGR
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGT0(The last
value is a zero.)
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_0A(The
second to last character is a zero.)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_0S(The
second to last character is a zero.)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PC
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PE
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PH
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PM
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PN
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PP
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PT
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
Application\PFM
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
Application\PFM-HealthCheck
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVer
sion\Uninstall\{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
In an environment in which an upgrade from version 7 or earlier has been performed, you
also need to perform the procedures described in this section for version 7.
#
1
2
3
4
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGT0(The last value is a zero.)
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_0A(The
second to last character is a zero.)
Note: If other Hitachi Command Suite products have been installed, the registry key name
Hitachi might be displayed as HITACHI (in all upper-case letters).
b) Make sure that the shared files indicated below do not exist.
If these files exist, delete them manually.
#
1
2
3
4
5
6
7
8
9
10
11
12
Note: The {vvrrss} part in the file names is a string of alphanumeric characters that indicates
302
At present, in version 8 and later, you do not need to perform the procedures described in this section.
However, you might need to perform them in the future.
In an environment in which an upgrade from version 7 or earlier has been performed, make sure that
you perform these procedures.
(1) Execute the Tuning Service uninstaller.
a) Open a command prompt.
b) Start the registry editor and make sure that the registry key indicated below exists.
If this key does not exist, go to step (2) in section 3-h.5.2.5.
#
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
Registry Key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
1
HiCommandTuningService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\
2
HTM-Tuning Service
3
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
3-h.5.2.6
In an environment in which an upgrade from version 7 or earlier has been performed, you also need
to perform the procedures described in this section for version 7. When you do so, replace the
303
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninst
all\{465EF71F-B608-4C33-9E19-D56DDCADC82A}
Command to execute
{UninstallString-value}/NOREBOOTNOFLAGOFF (: a single-byte space)
Note: Make sure that the Services applet is closed when executing the uninstaller.
e) Open the following file and make sure that the termination status has been output.
If the termination status has been output, the uninstallation has finished. Ignore any other output
values.
#
File Name
%SystemDrive%\htmpruninst.rtn
Note: If the file does not exist, the uninstallation is still in progress.
Note: Uninstallation might take five or more minutes to finish.
(2) Make sure that the registry keys indicated below do not exist.
a) Make sure that the registry keys indicated below do not exist.
If these registry keys exist, delete them manually.
# Registry Key
304
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
1
PerformanceReporter64
(When x86 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\HTMPR
2
(When x64 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\HTMPR
3
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
In an environment in which an upgrade from version 7 or earlier has been performed, you
also need to perform the procedures described in this section for version 7.
#
Registry Key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerformanceReporter
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\HTMPR
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{465EF71
F-B608-4C33-9E19-D56DDCADC82A}
Note: If other Hitachi Command Suite products have been installed, the registry key name
Hitachi might be displayed as HITACHI (in all upper-case letters).
3-h.5.2.7
In an environment that satisfies any of the conditions listed below, two different instances of Hitachi
Command Suite Common Component (for 32bit OS and for 64bit OS) might be installed:
- Hitachi Command Suite version 7 or earlier is currently installed or was previously installed.
- File Services Manager is currently installed or was previously installed.
- Storage Navigator Modular 2 is currently installed or was previously installed.
(1) Forcibly deleting the 32-bit version of Hitachi Command Suite Common Component
a) Copy the command indicated below to the directory of the OS system drive. If the file does not
exist, go to step (2).
#
File
305
The above directory is the default installation directory of the 32-bit version of Hitachi
Command Suite Common Component.
Be sure not to mistake the directory "Base64" for the directory "Base", because they might
be in the same directory.
b) Open a command prompt, and then move to the directory of the OS system drive.
c) Execute the command indicated below. Respond to all questions with Yes.
#
1
Command line
HBuninst /X
d) After the dialog box that indicates termination of the command appears, check the
value that was output to the following file.
#
1
File
hcmdsrtn.enf
If the value is 2, restart the OS, and then re-execute the command described in step (1) c).
If the value is not 2, or if the value is still 2 after re-execution, restart the OS, and then go to step
(2).
(2) Forcibly deleting the 64-bit version of Hitachi Command Suite Common Component
a) Copy the command indicated below to the directory of the OS system drive. If the file does not
exist, go to step (3).
If you forcibly deleted the 32-bit version of Hitachi Command Suite Common Component, a
file with the same name might exist in the copy destination. In such a case, be sure to overwrite
the file.
#
1
File
To earlier than Ver.8.1
%SystemDrive%\Program Files\HiCommand\Base64\tmp\HBuninst.exe
Ver.8.1 or later
%SystemDrive%\Program Files\HiCommand\Base64\tmp\HB64uninst.exe
Note:
The above directory is the default installation directory of the 64-bit version of Hitachi
Command Suite Common Component.
b) Open a command prompt, and then move to the directory of the OS system drive.
c) Execute the command indicated below. Respond to all questions with Yes.
#
1
Command line
To earlier than Ver.8.1
HBuninst /X
306
Ver.8.1 or later
HB64uninst /X
d) After the dialog box that indicates termination of the command appears, check the value that
was output to the following file.
#
1
File
hcmds64rtn.enf
If the value is 2, restart the OS, and then re-execute the command described in step (2) c).
If the value is not 2, or if the value is still 2 after re-execution, restart the OS, and then go to step
(3).
Start the registry editor and make sure that the following registry keys do not exist.
*1: Before deleting the registry, check the value of the PRODUCT CODE.
If these registry keys exist, delete them manually.
#
1
HiCommand Base 64
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\
2
HiRDBEmbeddedEdition_HD1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3
HBase64StgMgmtWebService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
4
HBase64StgMgmtSSOService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
5
HBase64StgMgmtWebSSOService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
6
HiRDBEmbeddedEdition_HD1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\
7
HBase64 Event
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\
8
HBase64 Storage Mgmt Log
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\
9
HiRDBEmbeddedEdition_HD1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
10
{1345FCD1-713E-4449-8F76-3F6503941040} (*1)(*2)
In an environment in which an upgrade from version 7 or earlier has been performed, you
307
also need to perform the steps shown below in the old environment (version 7 or earlier)
*1: Before deleting the registry, check the value of the PRODUCT CODE.
#
1
HiCommand Base
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\
2
HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3
HBaseStgMgmtComService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
4
HiRDBClusterService_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
5
HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
6
Application\HBase Storage Mgmt Log
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
7
Application\HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
8
Application\HitachiWebServer
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
9
{1345FCD1-713E-4449-8F76-3F6503941040} (*1) (*2)
*2: The value of the registry key of HiRDB is changed for every installation. Therefore, check
a value by the following methods.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\HiRDBEmb
eddedEdition_HD0.
V8.0.0 or later
Check the value in "Value data" for the InstallGuid value in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\
HiRDBEmbeddedEdition_HD1\<CurrentVersion>
<CurrentVersion> is equal to the value in "Value data" for the CurrentVersion value
in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\HiRDBEmb
eddedEdition_HD1.
Note: If other Hitachi Command Suite products have been installed, the registry key name
Hitachi might be displayed as HITACHI (in all upper-case letters).
(4) Delete the temporary directories for installation.
If the following directories exist, delete them manually.
#
Directory
%temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
%SystemDrive%\_HDBInstallerTemp
3-h.5.2.8
In an environment in which an upgrade from version 7 or earlier has been performed, you also
need to perform the steps shown below in the old environment (version 7 or earlier)
(1) Delete the Tuning Manager server database files.
a) Open the files indicated below.
If the files do not exist, go to step (2) in section 3-h.5.2.8.
#
1
2
File name
Hitachi-Tuning-Manager-installation-directory\inst\db_area.properties
Hitachi-Tuning-Manager-installation-directory\inst\db_area_6.properties
b) In these files, check the values of the properties indicated below, which indicate the
database file directories. Note that the db_areapath2 property might not be specified in the
file.
#
Property Name
309
db_areapath1
db_areapath2
c) Delete the directories specified as the values of the db_areapath1 and db_areapath2
properties.
If the directories do not exist, go to step (2) in section 3-h.5.2.8.
(2) Delete the database files used by Hitachi Command Suite Common Component.
Delete the directory you wrote down in step (1) of section 3-h.5.2.3.
If the directory does not exist, go to section 3-h.5.2.9.
If no file existed in step (1) a) of section 3-h.5.2.3, go to section 3-h.5.2.9.
3-h.5.2.9
Directory
<Installation directory>
%ProgramFiles%\InstallShield Installation Information\
2
{89331AB6-2E76-4986-9458-54795EF060A0}
%ProgramFiles%\InstallShield Installation Information\
3
{639938A4-41F1-4643-c5E9-05B1CAC6DA21}
%ProgramFiles%\InstallShield Installation Information\
4
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
%ProgramFiles%\InstallShield Installation Information\
5
{1345FCD1-713E-4449-8F76-3F6503941040}
%ProgramFiles%\InstallShield Installation Information\
6
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
%ProgramFiles%\InstallShield Installation Information\
7
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\
HiCommand Tuning Manager
1
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\
HiCommand Tuning Manager
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
2
HiCommandTuningManager64
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3
TuningManagerRESTService
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
4
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
5
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
Note: If other Hitachi Command Suite products have been installed, the registry key name
Hitachi might be displayed as HITACHI (in all upper-case letters).
In an environment in which an upgrade from version 7 or earlier has been performed, you
also need to perform the steps shown below in the old environment (version 7 or earlier)
#
1
HiCommandTuningManager
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
2
Application\TuningManager
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
3
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
Make sure that the registry keys indicated below do not exist. If these registry keys exist,
delete them.
# Registry Key(For V8 or later)
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi
1 HiCommand Base 64
2 HiCommand Tuning Manager
3 HiRDBEmbeddedEdition_HD1
4 HTMPR
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi
5
HiCommand Tuning Manager
6
JP1PC
7
JP1PCMGR
8
JP1PCAGT0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
9 HBase64StgMgmtWebService
10 HBase64StgMgmtSSOService
11 HBase64StgMgmtWebSSOService
12 HiCommandTuningManager64
311
13 PerformanceReporter64
14 TuningManagerRESTService
15 HiCommandTuningService
16 HiRDBClusterService_HD0
17 HiRDBEmbeddedEdition_HD1
18 JP1PCAGT_0A
19 JP1PCAGT_0S
20 JP1PCMGR_PC
21 JP1PCMGR_PE
22 JP1PCMGR_PH
23 JP1PCMGR_PM
24 JP1PCMGR_PN
25 JP1PCMGR_PP
26 JP1PCMGR_PS
27 JP1PCMGR_PT
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application
28 HBase64 Event
29 HBase64 Storage Mgmt Log
30 HiRDBEmbeddedEdition_HD1
31 PFM
32 PFM-HealthCheck
33 TuningManager
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
34 {89331AB6-2E76-4986-9458-54795EF060A0}
35
36
37
38
39
40
{639938A4-41F1-4643-c5E9-05B1CAC6DA21}
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
{1345FCD1-713E-4449-8F76-3F6503941040}
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
Note: If other Hitachi Command Suite products have been installed, the registry key name
Hitachi might be displayed as HITACHI (in all upper-case letters).
In an environment in which an upgrade from version 7 or earlier has been performed, you also
need to perform the steps shown below in the old environment (version 7 or earlier)
# Registry Key(For V7 or earlier)
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi
1 HiCommand Base
2 HiRDBEmbeddedEdition_HD0
3 HTMPR
4 JP1PC
5 JP1PCMGR
6 JP1PCAGT0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
7 HBaseStgMgmtComService
8 HBaseStgMgmtWebService
9 HBaseStorageMgmtWebSSOService
10 HiCommandTuningManager
11 HiCommandTuningService
12 HiRDBClusterService_HD0
13 HiRDBEmbeddedEdition_HD0
14 PerformanceReporter
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application
15 HBase Storage Mgmt Log
16 HiRDBEmbeddedEdition_HD0
17 HitachiWebServer
18 HTM-Tuning Service
312
b)
Directory
Hitachi Command Suite-Common-Component-installation-directory\bin
Command line
hcmds64intg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ"
represents a one-byte space)
If TuningManager is included in the output results, as shown in the output example below, go
to the next step. If TuningManager is not included, go to section 3-h.5.2.12.
Output example
Command line
hcmds64intg
/delete
/type
"INTERNALHRXJIHVZ"
TuningManager
/user
"htnmrepuser"
( represents a one-byte space)
/pass
d) Execute the command indicated below. Make sure that TuningManager is not included in
the output results.
#
Command line
313
Purpose
This appendix provides an overview of deleting Tuning Manager server for Linux, and describes the
following procedures (which are not disclosed to users):
- Procedure for deleting Tuning Manager server without deleting Agent
- Procedure for forcibly deleting the Tuning Manager server manually
3-i.2
Applicable Versions
3-i.3
Figure 3-i.3-1 shows an overview of the process for deleting Tuning Manager server.
314
START
No
Yes
Forcibly Deleting
Stopping services.
Was the
uninstallation
successful?
Yes
No
Is the
/tmp/hcmdsrtn.enf
value 0?
No
Yes
END
Restarting the OS
Deleting packages
Restarting the OS
Deleting the HiCommand Device
Manager authentication information.
END
Figure 3-i.3-1 The flow of the deletion of the Tuning Manager server
315
Notes:
-
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, use the deletion procedure described in 3-i.4. Do not use the forced
deletion procedure described in 3-i.5. If you do, all Hitachi Command Suite products (including
Hitachi File Services Manager and Hitachi Storage Navigator Modular 2), including Agent, will
no longer start.
Only perform the forced deletion procedure described in section 3-i.5 if you cannot perform a
normal uninstallation.
Before you forcibly delete Tuning Manager server, make sure that Hitachi Command Suite
family (including Hitachi File Services Manager and Hitachi Storage Navigator Modular 2) of
products other than Tuning Manager server have not been installed. If such products have been
installed, uninstall them before forcibly deleting Tuning Manager server. For details about how
to uninstall a HiCommand product, see the maintenance manual or other manuals for the
product.
The deletion procedure described in this document does not change the settings of Hitachi
Command Suite family (including Hitachi File Services Manager and Hitachi Storage
Navigator Modular 2) of products (including Agents), such as HiCommand Device Manager,
that are installed on hosts other than the host on which Tuning Manager server is installed. To
change the settings of such products, see the maintenance manual or other manuals for the
products.
3-i.4
On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, uninstall Tuning Manager server as described below.
Value to specify
$CM_NOUNINST
# File name
Output results
316
Explanation
m_ss}.trc
uninstalled.
2 HTMPR_UNINST_LO
G_{MM-DD-YYYY_h
HTM - Performance
Reporter uninstallation
h_mm_ss}.trc
log
$CM_NOUNINST
Note: If an error occurs during the deletion procedure in 3-i.4, integrity of the environment will be
lost. If such an error occurs, you might need to completely delete the environment by using the
forced deletion procedure in 3-i.5.
Note: After performing the deletion procedure described in section 3-i.4, do not install Hitachi
Command Suite family (including Hitachi File Services Manager and Hitachi Storage Navigator
Modular 2) of products until you have re-installed Tuning Manager server.
3-i.5
3-i.5.1
Stopping Services
Command
cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
./hcmdssrv stop
(2) Execute the following command and make sure that all the services indicated in the output
results have stopped.
#
Command
./hcmds64srv status
Output results
KAPM06441-I The HiRDB service has already stopped.
KAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt Web Service
KAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt Web SSO Service
317
If the service statuses are not the same as those indicated in the above output results 10 minutes
after performing step (1), restart the OS, and then perform step (1) again. If the services still
have not stopped, go to section 3-i.5.2.
Depending on the status after uninstallation, some services might no longer exist. In this case,
make sure that all the displayed services have stopped.
3-i.5.2
(1) Write down the directory name specified for the initpath property in the file indicated below.
If this file does not exist, go to section 3-i.5.3.
#
File name
Property name
<HBase32-Installation-directory>/conf/hcmdsdbinit.ini
initpath
<HBase64-Installation-directory>/conf/hcmdsdbinit.ini
initpath
3-i.5.3
In an environment that satisfies any of the conditions listed below, two different instances of Hitachi
Command Suite Common Component (for 32bit OS and for 64bit OS) might be installed:
- Hitachi Command Suite version 7 or earlier is currently installed or was previously installed.
- File Services Manager is currently installed or was previously installed.
- Storage Navigator Modular 2 is currently installed or was previously installed.
(1) Forcibly deleting the 32-bit version of Common Component and HiRDB
The installation directory of the 32-bit version of Common Component is shown below. Note
that this is the default directory path.
#
/opt/HiCommand/Base
318
a)
Command
cd <HBase32-Installation-directory>/bin/
./hcmdscancel PerformanceReporter
./hcmdscancel TuningManager
b)
Copy the file indicated below to a valid directory. If this file does not exist, go to step (2) in
this section.
#
File to copy
/var<HBase32-Installation-directory>/tmp/HBuninst.sh
Directories to which you must not copy the file (including subdirectories)
<Hitachi-Command-Suite-products-Installation-directory>
/opt/jp1pc
/var<Hitachi-Command-Suite-products-Installation-directory>
/tmp
Note:
The default path of <Hitachi-Command-Suite-products- Installation-directory> is:
/opt/HiCommand
c)
Command
cd <directory-to-which-HBuninst.sh-has-been-copied>
./HBuninst.sh /X
Note:
/X is an option, not a directory.
If the Hitachi Command Suite services are active during the command execution, restart the
OS, and then re-execute the commands.
When you execute the command, the message indicated under "Output result 1" is output. Enter
Yes for this message.
Output result 1
KAPM04315-W All the files for HBASE will now be deleted. Is this OK? Yes/No:
The message indicated under "Output result 2" is output. Enter Yes for this message
Output result 2
KAPM04316-W Are you sure you want to delete all of the files? Yes/No:
319
d)
File
/tmp/hcmdsrtn.enf
i)
If the value is 0:
Go to step (2) in this section.
ii)
If the value is 1:
Restart the OS, and then perform step (1) c) in this section.
Regardless of the execution results, go to step (2) in this section.
(2) Forcibly deleting the 64-bit version of Common Component and HiRDB
The installation directory of the 64-bit version of Common Component is shown below. Note
that this is the default directory path.
#
/opt/HiCommand/Base64
a)
Command
cd <HBase64-Installation-directory>/sbin/
./hcmdscancel PerformanceReporter
./hcmdscancel TuningManager
b)
Copy the file indicated below to a valid directory. If this file does not exist, go to step (3) in
this section.
#
File to copy
320
Directories to which you must not copy the file (including subdirectories)
<Hitachi-Command-Suite-products-Installation-directory>
/opt/jp1pc
/var<Hitachi-Command-Suite-products-Installation-directory>
/tmp
Note:
The default path of <Hitachi-Command-Suite-products- Installation-directory> is:
/opt/HiCommand
c)
Command
cd <directory-to-which-HBuninst.sh/HB64uninst.sh-has-been-copied>
Ver.8.1 or later
./HB64uninst.sh /X
Note:
/X is an option, not a directory.
If the Hitachi Command Suite services are active during the command execution, restart the
OS, and then re-execute the commands.
When you execute the command, the message indicated under "Output result 1" is output. Enter
Yes for this message.
Output result 1
KAPM04315-W All the files for HBASE will now be deleted. Is this OK? Yes/No:
The message indicated under "Output result 2" is output. Enter Yes for this message
Output result 2
KAPM04316-W Are you sure you want to delete all of the files? Yes/No:
d)
File
/tmp/hcmds64rtn.enf
i)
If the value is 0:
321
If the value is 1:
Restart the OS, and then perform step (2) c) in this section.
Regardless of the execution results, go to step (3) in this section.
(3) Checking the deletion status of Hitachi Command Suite Common Component
If you performed only step (2), perform the steps in the following table.
Condition
Subsequent action
Go to section 3-i.5.7.
Go to section 3-i.5.4(1-2).
If you performed both steps (1) and (2), perform the steps in the following table.
Condition
Subsequent action
Go to section 3-i.5.7.
are 0
If at least one of the values output to hcmdsrtn.enf and
Go to section 3-i.5.4.
hcmds64rtn.enf is not 0
If hcmdsrtn.enf or hcmds64rtn.enf does not exist
3-i.5.4
/etc/init.d/hicommand-HDB
i
/sbin/insserv r /etc/init.d/hicommand-CWS
/sbin/insserv r /etc/init.d/hicommand-SSOS
/sbin/insserv r /etc/init.d/hicommand-DM
/sbin/insserv r /etc/init.d/hicommand-HDB
ii
rm /etc/init.d/hicommand-CWS
rm /etc/init.d/hicommand-SSOS
rm /etc/init.d/hicommand-DM
rm /etc/init.d/hicommand-HDB
iii
Delete the following files if the above command fails.
#
File
/etc/init.d/HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
/etc/rc0.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
/etc/rc1.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
/etc/rc2.d/S07HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
10
/etc/rc3.d/S07HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
11
/etc/rc5.d/S07HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
12
/etc/rc6.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
[RHEL]
Delete the following files.
#
File
323
/etc/init.d/HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
/etc/rc0.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
10
/etc/rc1.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
11
/etc/rc2.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
12
/etc/rc3.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
13
/etc/rc5.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
14
/etc/rc6.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
15
16
(1-2) If the value output to hcmds64rtn.enf is not 0 or the file hcmds64rtn.enf does not exist
[SLES]
Execute i to iii if the following files exist.
/etc/init.d/hicommand64-hcs_web
/etc/init.d/hicommand64-hcs_hweb
/etc/init.d/hicommand64-hcs_sso
/etc/init.d/hicommand64-hcs_hsso
/etc/init.d/hicommand64-hcs_dm
i.
/sbin/insserv r /etc/init.d/hicommand64-hcs_web
/sbin/insserv r /etc/init.d/hicommand64-hcs_hweb
/sbin/insserv r /etc/init.d/hicommand64-hcs_sso
/sbin/insserv r /etc/init.d/hicommand64-hcs_hsso
/sbin/insserv r /etc/init.d/hicommand64-hcs_dm
ii.
rm /etc/init.d/hicommand64-hcs_web
rm /etc/init.d/hicommand64-hcs_hweb
324
rm /etc/init.d/hicommand64-hcs_sso
rm /etc/init.d/hicommand64-hcs_hsso
rm /etc/init.d/hicommand64-hcs_dm
iii.
Delete the following files if the above command fails.
#
File
1
[RHEL]
Delete the following files.
#
File
/etc/init.d/HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.HD
B
10
/etc/rc0.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
11
/etc/rc1.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
12
/etc/rc2.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
13
/etc/rc3.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
14
/etc/rc5.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
15
/etc/rc6.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
325
HDB
16
17
NOTE:
If Hitachi Command Suite Common Component is installed in the default location,
<Base-installation-directory> is replaced with "opt.HiCommand.Base64".
If Hitachi Command Suite Common Component is installed in a location other than the default,
<Base-installation-directory> is replaced with a name in which "/", which indicates the hierarchy
of the directory specified as the installation directory, is replaced with ".".
In an environment in which an upgrade from version 7 or earlier has been performed, you also
need to perform the steps shown below in the old environment (version 7 or earlier).
[RHEL7.x, SUSE12]
Delete the following entries that were added to /etc/inittab, if exist them.
Entries to delete
penn: < number
>:wait:<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/etc/pdpwon_e
PDnn: < number
>:respawn:<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdd
PDnn: < number >:respawn: env LD_LIBRARY_PATH=
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdd
nn:double digit numbers
Make sure that the file to be deleted is the correct file, and then delete it.
(a) Check the contents of the following files.
Note that nn differs depending on the installation environment. If multiple such files are present,
check the contents of all of the files.
/usr/lib/systemd/system/2248-PDnn.service
/usr/lib/systemd/system/2248-PDnn-start.service
/usr/lib/systemd/system/2248-PDnn-stop.service
/usr/lib/systemd/system/2248-penn.service
nn: double digit numbers
Within the [Service] section of these files, locate a line that begin with "ExecStart=" or
"ExecStop=", and search for files whose paths contain the directory where Hitachi Command
Suite Common Component is installed.
Note: Do not delete the files you find until you execute the commands in step (b).
In the example below, Hitachi Command Suite Common Component is installed in the
"/opt/HiCommand/Base64" directory.
[Service]
ExecStart=/bin/sh /opt/HiCommand/Base64/HDB/etc/pdpwon_e
(b) To prevent the HiRDB services from starting automatically at the boot time.
Execute the following commands for the files you found in step (a).
systemctl disable 2248-PDnn.service
systemctl disable 2248-PDnn-start.service
systemctl disable 2248-PDnn-stop.service
systemctl disable 2248-penn.service
3-i.5.5
Restarting the OS
3-i.5.6
If the 32-bit and 64-bit versions of Hitachi Command Suite Common Component are installed,
perform the procedures for both versions.
Environment
variable
Value
name
1
PDDIR
<Hitachi-Command-Suite-Common-Component-Instal
lation-directory>/HDB
PDCONFPATH
<Hitachi-Command-Suite-Common-Component-Instal
lation-directory>/HDB/conf
LD_LIBRARY_PATH
<Hitachi-Command-Suite-Common-Component-Instal
lation-directory>/HDB/lib
Shell
bash
source <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/
pduxenv
sh
PDDIR=<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
PDCONFPATH=<Hitachi-Command-Suite-Common-Component-Installation-directory>/
HDB/conf
LD_LIBRARY_PATH=<Hitachi-Command-Suite-Common-Component-Installation-dire
ctory>/HDB/lib
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
csh/tcsh
Other shells
Command
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdstop f
(3) Execute the following command to confirm that a pdprcd process is running.
(4) If
Command
ps ef |grep pdprcd
the
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib/servers/pdprcd
328
Command
kill 9 <pdprcd-process-number>
Note: You can use the ps command to check the process number (PID) of pdprcd.
3-i.5.7
If there are no such files, proceed to (2). Note that these files
File Name
<TuningManager-Installation-directory>/inst/db_area.properties
<TuningManager-Installation-directory>/inst/db_area_6.properties
(b) In these files, check the values of the properties indicated below, which indicate the
database file directories. Note that the db_areapath2 property might not be specified in the
file.
#
File Name
db_areapath1
db_areapath2
(c) Delete the directories indicated by the properties db_areapath1 and db_areapath2. If there
are no such directories, proceed to (2).
3-i.5.8
Deleting Packages
Command
rpm -e HTNM
rpm -e htnm-server
Command
rpm e HTMPR
329
3-i.5.9
Directory
<TuningManager-Installation-directory>
/var<TuningManager-Installation-directory>
<Hitachi-Command-Suite-Common-Component-Installation-directory>
/var<Hitachi-Command-Suite-Common-Component-Installation-directory>
/opt/jp1pc
/etc/.hitachi/HBase
/etc/.hitachi/HBase64
/etc/.hitachi/HTNM
jp1pcstatsvr 22350/tcp
jp1pcvsvr 22286/tcp
jp1pcovsvr 22292/tcp
Execute the following commands to delete installed information, and then terminate the
commands.
#
Command
/etc/hitachi_setup
JP1/PFM - Manager
Use the following command to check the number of products that have been installed.
#
Command
/etc/.hitachi/bin/SHOWPP
If the command displays TOTAL: 0 products, delete the following directory and files.
If the execution result of the command is not zero, Agent might remain in any hosts on which
Tuning Manager has been installed.
If the instance of Agent is not necessary, execute "/etc/hitachi_setup" again to uninstall the
Agent. If "/etc/hitachi_setup" fails to uninstall the Agent, perform step 3-f.
To use Agent after making forcible deletion of Tuning Manager, perform step 3-i.5.10.
#
Directory
/etc/.hitachi
330
Files
/etc/hitachi_start
/etc/hitachi_setup
Directory
<Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
Command line
If TuningManager is included in the output results, as shown in the output example below,
go to the next step. If TuningManager is not included, the procedure ends.
Output example
Primary Server : 127.0.0.1
Product Name :
DeviceManager
TuningManager
Command line
hcmds64intg -delete -type TuningManager -user "htnmrepuser" -pass " INTERNAL
HRXJIHVZ"
331
d) Execute the command indicated below. Make sure that TuningManager is not included in
the output results.
#
1
Command line
hcmds64intg -print -user "htnmrepuser" -pass " INTERNAL HRXJIHVZ"
332
3-j Force uninstall of the Tuning Manager agents for Windows (Ver.8 or later)
3-j.1
Purpose
This is the procedure for how to delete the agents (Windows) of Hitachi Tuning Manager in force.
3-j.2
Support version
All of the following agents of HiCommand Tuning Manager for Windows 8.0.0-00 or later
#
Agent
Version
OS
RAID Agent
8.0.0-00 or later
Windows
8.0.0-00 or later
Windows
Switch Agent
8.0.0-00 or later
Windows
NAS Agent
8.0.0-00 or later
Windows
Oracle Agent
8.0.0-00 or later
Windows
SQL Agent
8.0.0-00 or later
Windows
information is still remained which does not affect the re-install of the agents.
333
3-j.4
No
of the agent
Yes
Stop the agent related service
Reboot the OS
Both conditions
in (*1) met?
No
Yes
Use the htnmagtregclean
command to delete the registry
Reboot the OS
End
Figure 3-j.4-1 The flow of the deletion of the agent and re-install the agent
334
3-j.5
Command Suite Tuning Manager Installation Guide. If the attempt for uninstalling the agent
successfully ends, then following window of the completion of uninstall is shown.
3-j.6
3-j.6.1
(1) Change the type of the start up of the agent related service
a) Start the service applet
b) Change the type of the start up of the following agent related services into [manual].
[Note] Some of the following service may not be shown depending on the installation
configuration or the uninstall status described in section 3-j.4.
335
10
11
PFM - Correlator
12
13
14
15
16
17
18
19
20
21
336
The characters xxxx indicates the type of the agent, the characters yyyy indicates the instance
name of the agent when the agent is multi instance type agent. Following table shows the type of
agent and single/multi instance agent information.
Agent
RAID Agent
RAID
Multi Instance
RAID Map
Single Instance
Windows
Single Instance
MSExchange
Single Instance
Switch Agent
SANSwitch
Multi Instance
NAS Agent
NAS
Multi Instance
Oracle Agent
Oracle
Multi Instance
SQL Agent
Multi Instance
[*1] Agent for Server System consists of 3 agents, RAID Map/Windows/Exchange agent.
3-j.6.2
File Name
(c) Paste the character string of the second line into the command prompt, and then execute the
command. The uninstallation will start.
#
Command to execute
{UninstallString-command}
337
(b) Check whether following registry key exists or nor in registry editor. If the registry key does
not exist, go to the chapter 3-j.6.3
<Windows (x86)>
#
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC\PathName
<Windows (x64)>
#
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC\
PathName
(c)The value of the entry Path00 of the registry key in (b) is the installation directory of the
agent.
3-j.6.3
Command
rd /S /Q <Agent Installation Directory>
Deleting the registry keys (by using the htnmagtregclean command (version 2.0.0) )
The following are the prerequisites for using the htnmagtregclean command.
#
Supported OS
Architecture
Note
x86
x64
Including R2.
x64
Including R2.
Agent
Version
RAID Agent
8.0.0-00 or later
8.0.0-00 or later
Switch Agent
8.0.0-00 or later
NAS Agent
8.0.0-00 or later
338
Oracle Agent
8.0.0-00 or later
SQL Agent
8.0.0-00 or later
Notes
Only users with administrator privileges can use the htnmagtregclean command. If a user
without administrator privileges attempts to execute the command, the registry keys might not
be deleted, and records might not be output to the log file.
Before executing the htnmagtregclean command, all agent-related services must be stopped. If
an agent-related service is running and an attempt is made to execute the command, the
registry keys might not be deleted.
The results of executing the htnmagtregclean command are output to a log file
(htnmagtregclean.log), which is directly under the system drive. Make sure that the available
space on the system drive is not less than the size indicated below. If there is not enough
available space, records might not be output to the log file.
< Output log file size >
(10+n)KB
If there is already a log file that contains information, new entries are added to the existing
file. For this reason, do not make the log file read-only. If the file is read-only, no log data will
be output to the file.
4
If the User Account Control (UAC) function is being used in Windows Server 2008 and
Windows Server 2012, use an elevated command prompt that has administrator privileges to
execute the htnmagtregclean command. Move the mouse pointer over the command prompt
icon, and then right-click it. A context menu appears. From this menu, select Run as
administrator to start an elevated command prompt that has administrator privileges. If you
attempt to use an unelevated command prompt to execute the htnmagtregclean command, the
registry keys might not be deleted.
After you execute the htnmagtregclean command, delete the log file.
During execution, do not cancel the htnmagtregclean command by Windows operations such
as pressing [Ctrl] + [C] (however, interrupting the command by responding to messages is
permitted). If you cancel the command, you must re-execute it.
339
The htnmagtregclean command can be used to delete the following registry keys:
<Windows (x86)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
<Windows (x64)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
(1) Start a command prompt. If the UAC function is being used in Windows Server 2008 and
Windows Server 2012, start an elevated command prompt that has administrator privileges.
Command
htnmagtregclean
To continue, enter [y] or [Y]. To cancel the command, enter [n] or [N].
(4) Check the end code that appears in the command prompt in response to the htnmagtregclean
command.
End code
Processing Result
Log File
%SystemDrive%\htnmagtregclean.log
The reasons an attempt to delete one or more registry keys fails, and the corresponding
actions to be taken, are described in the following table.
#
Cause
user
Action
without
privileges attempted to execute the group, and then re-execute the htnmagtregclean
htnmagtregclean command.
2
command.
In the access permission settings for a Open the registry editor, and then disable the Deny
registry key, Deny has been specified setting for Delete Permission in the access
the
OS,
and
then
re-execute
the
htnmagtregclean command.
4
If the UAC function is being used in Move the mouse pointer over the command prompt
Windows Server 2008 and Windows icon, and then right-click it. A context menu appears.
Server 2012, no attempt is made to From this menu, select Run as administrator to
use an elevated command prompt that start an elevated command prompt that has
has
administrator
execute
the
privileges
command.
341
(5) After using the htnmagtregclean command to delete the registry keys, delete the log file.
#
Log File
%SystemDrive%\htnmagtregclean.log
01/06/2010
12:01:38.33
(I)
The
following
registry
key
exists:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_WS_Bro1
Wed 01/06/2010 12:01:38.33 (I) The following registry key was removed successfully:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_WS_Bro1
01/06/2010
12:01:38.33
(I)
The
following
registry
key
exists:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_WA_Bro1
Wed 01/06/2010 12:01:38.33 (W) An attempt to remove the following registry key has failed:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_WA_Bro1
342
3-j.6.4
(1) Check whether following registry keys exist or nor by using registry editor, and if exist, delete
them by manually. Registry key may not exist, depending on the status of installation or version.
<Windows (x86)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
<Windows (x64)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
3-j.6.5
Reboot the OS
343
3-k Force uninstall of the Tuning Manager agents for UNIX (Ver.8 or later)
3-k.1
Purpose
This is the procedure for how to delete the agents for UNIX (Solaris (SPARC)/Solaris
(x64)/HP-UX/AIX/Linux) of Hitachi Tuning Manager in force.
3-k.2
Support version
All of the following agents of HiCommand Tuning Manager for Unix 8.0.0-00 or later
#
Agent
Version
OS
RAID Agent
8.0.0-00 or later
8.0.0-00 or later
Switch Agent
8.0.0-00 or later
Linux
NAS Agent
8.0.0-00 or later
Linux
Oracle Agent
8.0.0-00 or later
DB2 Agent
8.0.0-00 or later
AIX/Linux
EAP Agent
8.0.0-00 or later
Solaris(SPARC), HP-UX
information is still remained which does not affect the re-install of the agents.
(*1) Including its bug fix version
344
3-k.4
Figure 3-k.4-1 shows the flow of the deletion of the agent and the flow of re-install the agent.
Start
Uninstaller
No
Normally End
Yes
Delete the file/directory
Reboot the OS
End
Figure 3-k.4-1 The flow of the deletion of the agent and re-install the agent
3-k.5
Uninstall the agent by following with the procedure described in the following manual:
Hitachi Command Suite Tuning Manager Installation Guide
If the attempt for uninstalling the agent successfully ends, then following message that indicates
the completion of uninstall is shown.
(Example) The case of RAID Agent
Mon Sep 28 12:00:00 GMT 2007
Done uninstalling HiCommand Tuning Manager - Agent for RAID
If the attempt for uninstall the agent does not successfully end, go to the chapter 3-k.6 to delete the
agent installation environment in force.
345
3-k.6
3-k.6.1
Command
1
cd /opt/jp1pc/tools
./jpcstop all
Command
1
cd /opt/jp1pc/htnm/bin
Command
rm -rf /opt/jp1pc/jpc_start
For AIX:
rmitab jp1pc
For SUSE Linux:
chkconfig jp1_pc off
Command
For AIX:
rmitab AgtRestApp
1
rmitab AgtRestWebSrv
For SUSE Linux:
chkconfig --del htnm_agent_rest_app
chkconfig --del htnm_agent_rest_webservice
346
Command
For Solaris:
cd /opt/HiCommand/Base/bin
For Linux:
cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
3-k.6.2
./hcmds64srv -stop
File Name
Command
1
cd /opt/jp1pc/htnm/bin
(c) Execute the following command in the console. The uninstallation will start in the console.
#
Command to execute
For Linux:
/etc/hitachi_x64setup
-f
-e
-u
-t
"<Agent
Installation
"<Agent
Installation
Directory>/htnm/Rest/system/PSB_INST.INF"
For AIX and HP-UX:
/etc/hitachi_setup
-f
-e
-u
-t
Directory>/htnm/Rest/system/PSB_INST.INF"
347
(a) Solaris
#
File
(b) Linux
#
File
(c) HP-UX
#
File
(d) AIX
#
File
Command
1
rm -rf /opt/jp1pc
348
3-k.6.3
Reboot the OS
Reboot the OS.
349
[In Windows]
In this procedure, installation destination of Hitachi Storage Command Suite Common Component is
hereinafter referred to as <Suite Install-dir>.
1. Start the Service Settings window, and confirm that the status of the following service is "Started".
[ In Ver.6 to earlier than 8 ]
HiRDB/EmbeddedEdition _HD0
[ In Ver.8 or later ]
HiRDB/EmbeddedEdition _HD1
3. Change current directory to "bin" directory of Hitachi Storage Command Suite Common
Component.
cd <Suite Install-dir>\bin
5. Change current directory to "bin" directory of the install directory of Hitachi Storage Command
Suite Common Component database.
cd <Suite Install-dir>\HDB\BIN
6. Execute the following command. (This command sets the environment variable that is necessary
for executing command of HiRDB. This command needs to be executed on the Command prompt
used in procedure 7.)
pdntcmd
After executing "pdntcmd" command, operate the following procedures a) d), then confirm that the
environment variable is set correctly.
a) Execute "set PATH" command to confirm that the following two paths are added to the result.
<Suite Install-dir>\HDB\BIN
<Suite Install-dir>\HDB\CLIENT\UTL
< When the above paths are not added >
Execute the following command manually to add the path. After executing the command, execute
"set PATH" command and confirm that the paths are added.
set PATH=<Suite Install-dir>\HDB\BIN;<Suite Install-dir>\HDB\CLIENT\UTL;%PATH%
b) Execute "set PDDIR" command and confirm that the result is following.
<Suite Install-dir>\HDB
< When the above character string is not defined in PDDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDDIR" command and confirm that the variable was defined correctly.
set PDDIR=<Suite Install-dir>\HDB
351
c) Execute "set PDCONFPATH" command and confirm that the result is following.
<Suite Install-dir>\HDB\CONF
< When the above character string is not defined in PDCONFPATH variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDCONFPATH " command and confirm that the variable was defined correctly.
set PDCONFPATH=<Suite Install-dir>\HDB\CONF
d) Execute "set PDUXPLDIR" command and confirm that the result is following.
<Suite Install-dir>\HDB\UXPLDIR
< When the above character string is not defined in PDUXPLDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDUXPLDIR" command and confirm that the variable was defined correctly.
set PDUXPLDIR=<Suite Install-dir>\HDB\UXPLDIR
b) In Ver.6 or later
pddbls -r HTnM -l
If the "STATUS" column is not "OPEN", it is likely that the target RD area is closed.
Following shows the status of RD area.
#
Status of RD area
Status of RD area
CLOSE
11
HOLD(INQ)
CLOSE HOLD
12
HOLD(CMD)
13
HOLD(BU)
CLOSE HOLD(CMD)
14
HOLD(BU I)
CLOSE HOLD(BU)
15
HOLD(BU W)
CLOSE HOLD(BU I)
16
HOLD(BU IW)
352
CLOSE HOLD(BU W)
17
ACCEPT-HOLD
18
OPEN
CLOSE ACCEPT-HOLD
10
HOLD
Purpose
In this chapter, how to extend the database log area temporarily, and how to change the
extended one to the default is described. This can be some recovery way when you face with the
polling problem of Main Console. If the service of Hitachi Tuning Manager has been stopped for
long time, or the attempt for polling has not been successfully ended for long time, Main Console
hit the polling problem due to large amount of data being tried to be inserted to the database, in
which amount of data exceeds the size of log area of the database.
[Note] The data is stored in the log are of the database until the data is committed.
The size of database log area can be extended, by adding the log files under the specified
directory. In this document, we call the specified directory as <Extended directory>.
[Note 1] More than 3.5 GB free space is required under <Extended directory>.
[Note2] Specify the path length of <Extended directory> within 60 characters.
[Note3] Use absolute path for specifying <Extended directory>. Note that Drive name should
be included in absolute path when OS is Windows.
[Note4] The character can be used as <Extended directory> are as follows.
( ) (For Windows )
Back Slush (For Windows, for specifying the directory relationship between the parent
353
We expect that polling problem is fixed after the database log area is extended, the criteria is
that each polling has been successfully completed within 50 minutes for more than 5 days.
The extension of the database log area is definitely temporarily solution, so is should be back to
the default after the polling problem fixed. Please note that the database log area should be back to
the default before upgrade installation, or uninstall is done for HTM. Thus, in this document, how
to back to the original setting of the database log area is also described.
4-c.2
Support version
4-c.3
4-c.3.1
354
Command
cd /d "<Suite Install-dir>\HDB\bin"
pdntcmd
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
#
Command
set PDDIR
Value
PDDIR
/opt/HiCommand/Base/HDB
PDCONFPATH
/opt/HiCommand/Base/HDB/conf
LD_LIBRARY_PATH
/opt/HiCommand/Base/HDB/lib
PATH
/opt/HiCommand/Base/HDB/bin
# kind of shell
bash
source /opt/HiCommand/Base/HDB/bin/pduxenv
sh
PDDIR=/opt/HiCommand/Base/HDB
PDCONFPATH=/opt/HiCommand/Base/HDB/conf
LD_LIBRARY_PATH=/opt/HiCommand/Base/HDB/lib
PATH=/opt/HiCommand/Base/HDB/bin:$PATH
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
export PATH
csh or tcsh
355
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
#
Command
Display result
PDDIR=/opt/HiCommand/Base/HDB
Command
(b) Create the database log file by executing the following command
Nothing is output when the command successfully ends.
#
Command
(c) Confirm that database log file is successfully created by executing the following command
#
Command
Display result
lg7
Command
Display result
lg8
Command
Display result
lg9
Command
Display result
lg10
357
Command
Display result
lg11
Command
Display result
lg12
358
iii) Add the following definition at the end of the sds01 file
pdlogadfg -d sys -g log7 ONL
pdlogadfg -d sys -g log8 ONL
pdlogadfg -d sys -g log9 ONL
pdlogadfg -d sys -g log10 ONL
pdlogadfg -d sys -g log11 ONL
pdlogadfg -d sys -g log12 ONL
[Note 1] Change the name of the <Extended directory> into the specified directory name.
[Note 2] Add the line return at the end of the file.
iv) Save the contents of sds01 file, and then close the sds01 file.
359
v) Confirm that the message is output like Display result by executing the following
command.
#
Command
pdconfchk
Display result
KFPS05007-I System definition check ended. return code = 0
vi) Confirm that database log file of log7 log12 is successfully added to the system by
executing the following command.
#
Command
pdlogls -d sys
Display result
HOSTNAME : NUCSTG02(******)
***** Off-line Information *****
Group
Type Server
Gen No.
Status Run ID
log1
sys
sds01
1 cnu---u 44ffbe81
318b
--------
log2
sys
sds01
2 cnu---u 44ffbe81
318c
43d1
--------
log3
sys
sds01
3 cnu---u 44ffbe81
43d2
561c --------
log4
sys
sds01
4 cnu---u 44ffbe81
561d
64a2
--------
log5
sys
sds01
5 cnu---u 44eec6db
91cd
ce07
--------
log6
sys
sds01
6 cnu---u 44eec6db
ce08
ed57
--------
log7
sys
sds01
0 cn----- 00000000
--------
log8
sys
sds01
0 cn----- 00000000
--------
log9
sys
sds01
0 cn----- 00000000
--------
log10
sys
sds01
0 cn----- 00000000
--------
log11
sys
sds01
0 cn----- 00000000
--------
log12
sys
sds01
0 cn----- 00000000
--------
360
Block No.
Ex-Status
4-c.3.3
Windows
cd /d "<Suite Install-dir>\bin"
Solaris
cd /opt/HiCommand/Base/bin
./hcmdsdbsrv -start
(2) Confirm that the service is running by executing the following command. If the service is
running, the message is output like Display result.
#
Windows
Solaris
./hcmdsdbsrv -status
Display result
KAPM06440-I The HiRDB service has already started.
361
(3) Open the pdlog01 file *1, and confirm that KFPS01109-W message is not output between
KFPS01803 message and KFPS01813 message.
(*1) If the pdlog02 file exists, open the pdlog02 file instead of pdlog01 file.
Display result
KFPS01803-I HiRDB unit unt1 start mode determined. start mode:S
KFPS01001-I s1 assigned as current logical status file. server kind:01 server:sds01
KFPS01221-I log1 assigned as current file group of sys(sds01) log file. generation number=1,
KFPS02183-I Syncpoint dump for sds01 has been acquired to file group spd1. log file
KFPS01813-I Server sds01 started
If KFPS01109-W message is not output, it means database log area is successfully extended.
If KFPS01109-W message is output, it means that database log area is not successfully
extended, and the possible cause is that the described procedure of database log area extension is
not surely performed. In this case, execute the procedure described in the chapter 4-c.3.1, 4-c.3.2,
4-c.3.3 again.
4-c.4
4-c.4.1
Command
362
cd /d "<Suite Install-dir>\HDB\bin"
pdntcmd
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
#
Command
set PDDIR
Display result
PDDIR=<Suite Install-dir>\HDB
363
Value
PDDIR
/opt/HiCommand/Base/HDB
PDCONFPATH
/opt/HiCommand/Base/HDB/conf
LD_LIBRARY_PATH
/opt/HiCommand/Base/HDB/lib
PATH
/opt/HiCommand/Base/HDB/bin
# kind of shell
bash
source /opt/HiCommand/Base/HDB/bin/pduxenv
sh
PDDIR=/opt/HiCommand/Base/HDB
PDCONFPATH=/opt/HiCommand/Base/HDB/conf
LD_LIBRARY_PATH=/opt/HiCommand/Base/HDB/lib
PATH=/opt/HiCommand/Base/HDB/bin:$PATH
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
export PATH
csh or tcsh
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
#
Command
Display result
PDDIR=/opt/HiCommand/Base/HDB
364
Command
[Note] When the extended database log file is not used, KFPS01273-E reason code=1607-0"
and "KFPS01280-E1601-0" message is output, but please ignore it, this is no problem.
Display result
KFPS01273-E Unable to change log file status. element file:log7, system A/B:a, reason code=1607-0
KFPS01280-E Unable to execute pdlogchg command due to 1601-0
Windows
<Suite Install-dir>\HDB\CONF
Solaris
/opt/HiCommand/Base/HDB/CONF
365
ii) Delete the contents added in the chapter 3.2 from sds01 file.
iii) Save the sds01 file and close it.
iv) Confirm that the message is output like Display result by executing the following
command.
#
Command
pdconfchk
Display result
KFPS05007-I System definition check ended. return code = 0
Command
366
(b) Confirm that the database log file is successfully deleted by executing the following
command.
When the database log file is successfully deleted, nothing is output.
#
Command
(5) Delete the file system to which the database log file is stored by executing the following
command.
#
Command
Confirm that rdX1, rdX2, rdX3, rdX4, rdX5, rdX6 are successfully deleted under
<Extended directory>.
(6) Confirm that the database log file is deleted from the system by executing the following
command.
When the database log file is successfully deleted from the system, the log 7 log 12 is not output
by the command.
367
Command
pdlogls -d sys
Display result
HOSTNAME : NUCSTG02(******)
***** Off-line Information *****
Group
Type Server
log1
sys
sds01
cnu---u
log2
sys
sds01
log3
sys
sds01
log4
sys
log5
log6
4-c.4.3
Gen No.
Status
Run ID
Block No.
Ex-Status
44ffbe81
318b
cnu---u
44ffbe81
318c
43d1
--------
cnu---u
44ffbe81
43d2
561c
--------
sds01
cnu---u
44ffbe81
561d
64a2
--------
sys
sds01
cnu---u
44eec6db
91cd
ce07
--------
sys
sds01
cnu---u
44eec6db
ce08
ed57
--------
--------
Windows
cd /d "<Suite Install-dir>\bin"
Solaris
cd /opt/HiCommand/Base/bin
./hcmdsdbsrv -start
(2) Confirm that the service is running by executing the following command. If the service is
running, the message is output like Display result.
#
Windows
hcmds64dbsrv /status
#
Solaris
./hcmdsdbsrv -status
Display result
KAPM06440-I The HiRDB service has already started.
(3) Open the pdlog01 file *1, and confirm that KFPS01109-W message is not output between
KFPS01803 message and KFPS01813 message.
(*1) If the pdlog02 file exists, open the pdlog02 file instead of pdlog01 file.
Display result
KFPS01803-I HiRDB unit unt1 start mode determined. start mode:S
KFPS01001-I s1 assigned as current logical status file. server kind:01 server:sds01
KFPS01221-I log1 assigned as current file group of sys(sds01) log file. generation number=1,
KFPS02183-I Syncpoint dump for sds01 has been acquired to file group spd1. log file
KFPS01813-I Server sds01 started
If KFPS01109-W message is not output, it means database log area is successfully changed to
the default.
If KFPS01109-W message is output, it means that database log area is not successfully changed
to the default, the possible cause is that the described procedure of how to change the database log
area to the default is not surely performed. In this case, execute the procedure described in the
chapter 4-c.4.1, 4-c.4.2, 4-c.4.3 again.
369
Appendix 6 For the HPE OEM version, substitute the following terms as
indicated
Notes in this guide are described HPE OEM version. When reading, replace the terms in the text
according to the following table.
[In Ver.6]
No.
Item
HITACHI version
HP OEM version
1.
Product
HP
. Names
2.
4.
5.
6.
7.
8.
XP
Tuning
Manager
.
3.
StorageWorks
StorageWorks
XP
Tuning
Server System
Oracle
RAID
SAN Switch
XP
Tuning
XP
Tuning
StorageWorks
XP
Tuning
XP
Tuning
9.
IBM(R)
10.
Component
StorageWorks
Universal Manager
DB2(R)
Agent
XP
Tuning
for
IBM(R)
Database
Common Component
XP Command
0 Names
View
AE
Suite
Common Component
.
11.
Abbreviation
HTnM
TunMgr
HDvM
Device Manager
%SystemDrive%\Program
%SystemDrive%\Program
Files\HiCommand\TuningManager
Files\CVXPAE\TuningManager
.
12.
13.
Default
2 installation
. directory
for
Tuning
Manager
server
(For
370
Windows
Server
2003
(x86)
and
Windows
Server
2008
(x86))
14.
Default
%SystemDrive%\Program
installation
(x86) \HiCommand\TuningManager
(x86) \CVXPAE\TuningManager
Default
%SystemDrive%\Program
%SystemDrive%\Program
installation
Files\HiCommand\Base
Files\CVXPAE\Base
directory
Files %SystemDrive%\Program
Files
for
Tuning
Manager
server
(For
Windows
Server
2003
(x64)
and
Windows
Server
2008
(x64))
15.
directory
for
Common
Component
(For Windows
Server
2003
(x86)
and
Windows
Server
2008
(x86))
16.
Default
%SystemDrive%\Program
installation
(x86) \HiCommand\Base
directory
Files %SystemDrive%\Program
Files
(x86) \CVXPAE\Base
for
Common
Component
(For Windows
Server
2003
(x64)
and
Windows
Server
2008
(x64))
371
17.
Related
3 documents
.
18.
Manager
.
19.
Tuning
software
StorageWorks
Manager
agent
XP
Tuning
software
server
administration guide
Hitachi Tuning Manager Software HP
XP
administration guide
Hitachi Tuning Manager Software HP
StorageWorks
User's Guide
StorageWorks
XP
Tuning
.
20.
.
21.
XP
Tuning
reports reference
.
23. 2
StorageWorks
Tuning
reference
.
22.
XP
StorageWorks
StorageWorks
XP
Tuning
StorageWorks
XP
Tuning
.
24. 2
XP
Tuning
.
25. 2 Subsystem
StorageWorks
configuration guide
Lightning 9910/9960
StorageWorks XP48/XP512
Lightning 9970V/9980V
StorageWorks XP128/XP1024
NSC55
StorageWorks XP10000
StorageWorks XP SVS200
USP100/USP600/USP1100
StorageWorks XP12000
USP V
StorageWorks XP24000
2 Names
.
26. 2
3
.
27. 2
4
.
28. 2
5
.
29. 2
6
.
30. 2
372
7
.
31. 2
USP_VM
StorageWorks XP20000
Thunder 9200
8
.
32. 2
9
.
33. 3
0
34.
AMS series
AMS200/AMS500/AMS1000
35.
AMS2000 series
AMS2100/AMS2300/AMS2500
36.
SMS100
37.
WMS100
38. 3 Command
hcmdsgetlogs
Cvxpaegetlogs
StorageWorks
2 Names
.
39. 3 Service
4 Names
.
40. 3
5
.
41. 3
6
XP
Performance
Reporter
.
42. 3 Start menu
9
AE
HiCommand_log.jar
cvxpae_logs.jar
44.
HiCommand_log.hdb.jar
cvxpae_logs.hdb.jar
45.
HiCommand_log.db.jar
cvxpae_logs.db.jar
46.
HiCommand_log.csv.jar
cvxpae_logs.csv.jar
.
43.
File Names
373
[In Ver.7]
No.
Item
HITACHI version
HP OEM version
1.
Product
. Names
Manager
or
HP P9000 Tuning Manager
2.
3.
4.
5.
6.
7.
8.
Server System
Oracle
RAID
SAN Switch
9.
IBM(R)
DB2(R)
Universal Manager
Database
10.
Agent
for
IBM(R)
Enterprise Applications
Applications
11.
Component
Common Component
XP Command
0 Names
View
AE
Suite
Common Component
.
12.
Abbreviation
HTnM
TunMgr
HDvM
Device Manager
%SystemDrive%\Program
%SystemDrive%\Program
Files\HiCommand\TuningManager
Files\CVXPAE\TuningManager
.
13.
14.
Default
2 installation
. directory
for
374
Tuning
Manager
server
(For
Windows
Server
2003
(x86)
and
Windows
Server
2008
(x86))
15.
Default
%SystemDrive%\Program
installation
(x86) \HiCommand\TuningManager
(x86) \CVXPAE\TuningManager
Default
%SystemDrive%\Program
%SystemDrive%\Program
installation
Files\HiCommand\Base
Files\CVXPAE\Base
directory
Files %SystemDrive%\Program
Files
for
Tuning
Manager
server
(For
Windows
Server
2003
(x64)
and
Windows
Server
2008
(x64))
16.
directory
for
Common
Component
(For Windows
Server
2003
(x86)
and
Windows
Server
2008
(x86))
17.
Default
%SystemDrive%\Program
installation
(x86) \HiCommand\Base
directory
Files %SystemDrive%\Program
Files
(x86) \CVXPAE\Base
for
Common
Component
(For Windows
Server
2003
(x64)
and
375
Windows
Server
2008
(x64))
18.
Related
3 documents
.
19.
Manager
Software
Agent
Administration Guide
Hitachi Tuning Manager Software HP StorageWorks P9000 Tuning
.
20.
Manager
Software
Server
Administration Guide
Hitachi Tuning Manager Software HP StorageWorks P9000 Tuning
User's Guide
.
21.
.
22.
.
23.
.
24. 2
0
Manager
Software
Application
Reports Reference
Hitachi Tuning Manager Software HP StorageWorks P9000 Tuning
Command Line Interface Guide
.
25. 2
Lightning 9910/9960
StorageWorks XP48/XP512
Lightning 9970V/9980V
StorageWorks XP128/XP1024
NSC55
StorageWorks XP10000
StorageWorks XP SVS200
USP100/USP600/USP1100
StorageWorks XP12000
.
26. 2 Subsystem
2 Names
.
27. 2
3
.
28. 2
4
.
29. 2
5
.
30. 2
376
6
.
31. 2
USP V
StorageWorks XP24000
USP_VM
StorageWorks XP20000
33.
VSP
StorageWorks P9500
34. 2
Thunder 9200
7
.
32. 2
8
.
9
.
35. 3
0
36.
AMS series
AMS200/AMS500/AMS1000
37.
AMS2000 series
AMS2100/AMS2300/AMS2500
38. S
SMS100
39.
HUS100 series
HUS110/HUS130/HUS150
40.
WMS100
41. 3 Command
hcmdsgetlogs
Cvxpaegetlogs
Tuning Manager
Tuning Service
Performance Reporter
2 Names
.
42. 3 Service
4 Names
.
43. 3
5
.
44. 3
6
.
45. 3 Start menu
9
AE
377
46.
File Names
HiCommand_log.jar
cvxpae_logs.jar
47.
HiCommand_log.hdb.jar
cvxpae_logs.hdb.jar
48.
HiCommand_log.db.jar
cvxpae_logs.db.jar
49.
HiCommand_log.csv.jar
cvxpae_logs.csv.jar
Item
HITACHI version
HP OEM version
1.
Product
Names
2.
Edition
3.
Hitachi Tuning Manager - Agent for HP XP7 Tuning Manager - Agent for
Server System
Server System
4.
Hitachi Tuning Manager - Agent for HP XP7 Tuning Manager - Agent for
Oracle
5.
Oracle
Hitachi Tuning Manager - Agent for HP XP7 Tuning Manager - Agent for
RAID
6.
RAID
7.
Hitachi Tuning Manager - Agent for HP XP7 Tuning Manager - Agent for
SAN Switch
8.
SAN Switch
Hitachi Tuning Manager - Agent for HP XP7 Tuning Manager - Agent for
Microsoft(R) SQL Server
9.
Hitachi Tuning Manager - Agent for HP XP7 Tuning Manager - Agent for
IBM(R)
DB2(R)
Universal IBM(R)
Database
10.
11.
Database
Hitachi Tuning Manager - Agent for HP XP7 Tuning Manager - Agent for
Component
Enterprise Applications
Enterprise Applications
Common Component
HP
Abbreviation
Command
View
HTnM
TunMgr
HDvM
DevMgr
Default
%SystemDrive%\Program
%SystemDrive%\Program
installation
Files\HiCommand\TuningManager
Files\CVXPAE\TuningManager
13.
14.
XP7
directory
AE
Common Component
Names
12.
Universal
DB2(R)
for
Tuning
Manager
server
(For
Windows
378
Server
2003
(x64)
and
Windows
Server
2008
(x64))
15.
Default
%SystemDrive%\Program
%SystemDrive%\Program
installation
Files\HiCommand\Base
Files\CVXPAE\Base
for
directory
Common
Component
(For Windows
Server
2003
(x64)
and
Windows
Server
2008
(x64))
16.
Related
documents
Manager
Agent
Guide
17.
Server
Guide
18.
19.
20.
Reference Guide
Hardware
Reference
21.
22.
Application
XP7
Tuning
Manager
Reference
23.
24.
25.
Reference Guide
Subsystem
Guide
Lightning 9910/9960
StorageWorks XP48/XP512
379
Names
26.
Lightning 9970V/9980V
StorageWorks XP128/XP1024
27.
NSC55
StorageWorks XP10000
28.
StorageWorks XP SVS200
29.
USP100/USP600/USP1100
StorageWorks XP12000
30.
USP V
StorageWorks XP24000
31.
USP_VM
StorageWorks XP20000
32.
VSP
StorageWorks P9500
33.
VSP G1000
XP7 Storage
34.
Thunder 9200
35.
AMS series
AMS200/AMS500/AMS1000
37.
AMS2000 series
AMS2100/AMS2300/AMS2500
38.
SMS100
39.
HUS100 series
HUS110/HUS130/HUS150
40.
41.
Command
WMS100
hcmdsgetlogs
Cvxpaegetlogs
Tuning Manager
Performance Reporter
Names
42.
Service Names
43.
44.
Start menu
AE
HiCommand_log.jar
cvxpae_logs.jar
46.
HiCommand_log.hdb.jar
cvxpae_logs.hdb.jar
47.
HiCommand_log.db.jar
cvxpae_logs.db.jar
48.
HiCommand_log.csv.jar
cvxpae_logs.csv.jar
45.
File Names
380
Item
HITACHI version
1.
Product
Names
2.
3.
Packard
Enterprise
XP7
Server System
System
4.
Oracle
5.
RAID
6.
7.
SAN Switch
Switch
8.
Manager
Agent
for
DB2(R)
Database
10.
Enterprise Applications
Manager
Agent
for
Enterprise Applications
11.
Component
Common Component
Names
View
AE
Common
Component
12.
Abbreviation
HTnM
TunMgr
HDvM
DevMgr
Default
%SystemDrive%\Program
%SystemDrive%\Program
installation
Files\HiCommand\TuningManager
Files\CVXPAE\TuningManager
13.
14.
directory
for
Tuning
Manager
server
(For
Windows
Server
2003
381
(x64)
and
Windows
Server
2008
(x64))
15.
Default
%SystemDrive%\Program
%SystemDrive%\Program
installation
Files\HiCommand\Base
Files\CVXPAE\Base
directory
for
Common
Component
(For Windows
Server
2003
(x64)
and
Windows
Server
2008
(x64))
16.
Related
documents
Manager
Agent
Administration Tuning
Guide
17.
Manager
XP7
Agent
Administration Guide
Server
Administration Tuning
Guide
Manager
Server
Administration Guide
19.
Enterprise
18.
Packard
20.
Hardware
Reference
21.
Reference
22.
Reports Reference
Application
Reference
23.
Reference
24.
25.
Subsystem
Lightning 9910/9960
StorageWorks XP48/XP512
26.
Lightning 9970V/9980V
StorageWorks XP128/XP1024
27.
NSC55
StorageWorks XP10000
28.
StorageWorks XP SVS200
29.
USP100/USP600/USP1100
StorageWorks XP12000
30.
USP V
StorageWorks XP24000
31.
USP_VM
StorageWorks XP20000
32.
VSP
StorageWorks P9500
33.
VSP G1000
XP7 Storage
34.
Thunder 9200
35.
Names
AMS series
AMS200/AMS500/AMS1000
37.
AMS2000 series
AMS2100/AMS2300/AMS2500
38.
SMS100
39.
HUS100 series
HUS110/HUS130/HUS150
40.
41.
Command
WMS100
hcmdsgetlogs
cvxpaegetlogs
Tuning Manager
Performance Reporter
Names
42.
Service Names
43.
44.
Start menu
AE
HiCommand_log.jar
cvxpae_logs.jar
46.
HiCommand_log.hdb.jar
cvxpae_logs.hdb.jar
47.
HiCommand_log.db.jar
cvxpae_logs.db.jar
48.
HiCommand_log.csv.jar
cvxpae_logs.csv.jar
45.
File Names
383
Purpose
This section describes the procedure for backing up the Tuning Manager server data and the Agent
database on a host on which these products are installed in a Windows environment.
7-a.2
Applicable Versions
7-a.3
Terms
Terms
Folder
Hitachi-StorageCommand-Suite-Common-Component
-installation-directory
<Installation-directory>\Base
1
[ In Ver.8 or later ]
<Installation-directory>\Base64
2
Hitachi-Tuning-Manager-installation-directory
<Installation-directory>\TuningManager
Installation-directory
3
Server 2012:
%SystemDrive%\Program Files (x86)\HiCommand
[ In Ver.8 or later ]
%SystemDrive%\Program Files\HiCommand
4
Agent-installation-directory
<Installation-directory>\TuningManager\jp1pc
Platform-Agent-Tuning-Manager-installation-directory
<Installation-directory>\TuningManager\jp1pc
Note: Unless you specify other directories during installation, the above directories are used by
default.
7-a.4
Figure 7-a.7-1 provides an overview of the procedure for backing up the Tuning Manager server data
and Agent database on a host on which these products are installed in a Windows environment.
384
Start
Described in 7-a.5 Back up data for Hitachi Storage Command
Suite products
7-a.5(1)
7-a.5(2)
Back up the definition information files for the Tuning Manager server
7-a.6
7-a.7
7-a.7(ii)
Start Agent
7-a.8(1)
7-a.8(2)
Stop Agent
7-a.9(1)
7-a.9(2)
7-a.10
7-a.11
7-a.12
End
Figure 7-a.7-1 An overview of the procedure for backing up the Tuning Manager server and Agent databases
385
7-a.5
Command line
cd <Hitachi-Tuning-Manager-installation-directory>\bin\
htm-db-status
Output example
KATN01314-I The command htm-db-status will now be executed.
Database Capacity (Used/Total): 15560 / 2048000 kBytes
Area Path:
D:\Program Files\HiCommand\TuningManager\database\TuningManager\TM00
KATN01309-I The database status has been displayed.
386
Command line
cd <Hitachi-Command-Suite-Common-Conponent-installation-directory>\bin\
Output example
KAPM05320-I Backup successfully ended : CommonComponent Database.
Note: For details about the hcmdsbackups command, see the manual.
7-a.6
Back up the definition information files for the Tuning Manager server
Use the Windows COPY command to back up the definition information files for the
Tuning Manager server. For a list of the Tuning Manager server definition information
files to back up, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
The following shows an example of using the Windows COPY command to back up the
definition information files for the Tuning Manager server. For this example, the
destination folders used by the COPY command must be created in advance.
#
Command line
COPY <Hitachi-Tuning-Manager-installation-installation-directory>\jp1pc\jpchosts
d:\backup\HiCommand\TuningManager\jp1pc
COPY<Hitachi-Tuning-Manager-installation-installation-directory>\jp1pc\*.ini
d:\backup\HiCommand\TuningManager\jp1pc
COPY <Hitachi-Tuning-Manager-installation-installation-directory>\jp1pc\bin\action\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\bin\action
COPY <Hitachi-Tuning-Manager-installation-installation-directory>\jp1pc\bin\statsvr\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\bin\statsvr
COPY <Hitachi-Tuning-Manager-installation-directory>\conf\user.properties
d:\backup\HiCommand\TuningManager\conf
COPY <Hitachi-Tuning-Manager-installation-directory>\conf\logging.properties
387
d:\backup\HiCommand\TuningManager\conf
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\clator\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\clator
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.DB
d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.IDX
d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.DAT
d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\store\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\store
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\store\*.DAT
d:\backup\HiCommand\TuningManager\jp1pc\mgr\store
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr\*.DB
d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr\*.IDX
d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\trapgen\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\trapgen
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr\viewsvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\data\*
d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr\data
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\reports\*
d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\agt0\agent\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\agt0\agent
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\agt0\store\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\agt0\store
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\ui.properties
d:\backup\HiCommand\TuningManager\system\sysconf
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\core.properties
d:\backup\HiCommand\TuningManager\system\sysconf
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\cli.properties
d:\backup\HiCommand\TuningManager\system\sysconf
388
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\common.properties
d:\backup\HiCommand\TuningManager\system\sysconf
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\system.logging.properties
d:\backup\HiCommand\TuningManager\system\sysconf
7-a.7
Use the Windows COPY command to back up the definition information files for
Performance Reporter. For a list of the Performance Reporter definition information
files to back up, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
The following shows an example of using the Windows COPY command to back up the
definition information files for Performance Reporter. For this example, the destination
folders used by the COPY command must be created in advance.
#
Command line
COPY <Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\conf\*.*
d:\backup\HiCommand\TuningManager\PerformanceReporter\conf
Back up the Performance Reporter bookmarks stored in the following folder, by using
the Windows XCOPY command to copy the folder in its entirety.
Folder
<Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\bookmarks
Note: The above folder is an example when the "bookmarkRepository" item of the
initialization settings file (config.xml) of Performance Reporter is not specified. Back up
Performance
Reporter
bookmarks
from
the
folder
specified
as
the
389
Command line
XCOPY /e /y /i
<Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\bookmarks
d:\backup\HiCommand\TuningManager\PerformanceReporter\bookmarks
7-a.7(ii) Back up the definition information files for Tuning Manager REST Application
Service (Ver. 8 or later)
In version 8.0.0 or later, if you are using Tuning Manager API, backup of definition
information files for Tuning Manager REST Application Service are required. Refer to
the following backup files.
# Directory
Backup files
1 <Hitachi-Tuning-Manager-installation-directory>\
system\
rest.properties
sysconf\
rest_raidinstance_info
rest_nasinstance_info
rest_host_info
7-a.8
Only perform this procedure for an Agent for which the data storage format is Store database. This
procedure is not necessary on an Agent that is operated with Hybrid Store.
(1) Start Agent.
Execute the commands indicated below.
#
Command line
cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
jpcstart all
Command line
cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
jpcctrl list *
folder specified with the -d option each time you execute the command.
Note:
If you back up multiple databases to the same specified folder, the data that is backed up might
be inconsistent. Make sure to change the folder each time you perform the backup operation.
The following shows an example of the jpcctrl backup command execution:
#
Command line
cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
mkdir d:\backup\DS1RAID[host01]
Output example
KAVE06000-I Backup processing of the Store database terminated normally. (service= DS1RAID[host01])
Note: For details about the jpcctrl backup command, see the manual.
7-a.9
Only perform this procedure for an Agent for which the data storage format is Store database. This
procedure is not necessary on an Agent that is operated with Hybrid Store.
(1) Stop Agent.
Execute the commands indicated below.
#
Command line
cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
jpcstop all
Note that files #5 and #6 might not exist in certain environments. If these files do not exist, the
"COPY" command will fail. However, the failure of this command does not affect the backup
operation.
#
Command line
COPY <Agent-installation-directory>\xxxx\agent\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\xxxx\agent
COPY <Agent-installation-directory>\xxxx\agent\instance-name\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\xxxx\agent\instance-name
COPY <Agent-installation-directory>\xxxx\store\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\xxxx\store
COPY <Agent-installation-directory>\xxxx\store\instance-name\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\xxxx\store\instance-name
COPY <Agent-installation-directory>\agtw\agent\agtw.properties
d:\backup\HiCommand\TuningManager\jp1pc\agtw\agent
COPY <Agent-installation-directory>\agtt\agent\jpcapp
d:\backup\HiCommand\TuningManager\jp1pc\agtt\agent
Note: xxxx indicates the service key of each Agent. For details on the service keys of
each Agent,
see 4.1.5. jpcras command.
7-a.10 Back up the definition information files for HTnM-Agent REST Services (Ver. 8 or
later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must back up the definition information files for HTnM-Agent REST Services. The files to back
up are listed in the following table.
#
Directory
Backup files
<Agent-installation-directory>\
2
3
4
htnm\
agent\
config\
5
6
apidataglobalconfig.ini
alertglobalconfig.ini
system\
data_file_manage
(Does not exist if Tuning Manager API is disabled.)
7
8
Rest\
config\
9
10
11
user.properties
htnm_httpsd.conf
system\
sysconf\
system.properties
392
7-a.11 Back up the performance data for Tuning Manager API (Ver. 8 or later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must back up the performance data for Tuning Manager API. When backing up performance
data for using in Tuning Manager API, copy the following directory/file.
[Note]
By editing the property file (apidataglobalconfig.ini or jpcagt.ini) the output destination of the
performance data can be changed. If the output destination for performance data has been changed,
copy the performance data from the changed output destination to the target directory/file.
#
Directory
Backup files/directories
<Agent-installation-directory>\
xxxx\
agent\
instance-name\
restdata\
Keeping
the
directory
structure,
copy
all
The following table lists an execution example of the htmhsbackup command in a Windows
environment.
#
Command line
cd <Agent-installation-directory>\jp1pc\htnm\bin
mkdir D:\backup\RAID_backup
393
the
7-b. Restore procedure on a host on which the Tuning Manager server and Agent are installed in
a Windows environment
7-b.1
Purpose
This section describes the procedure for restoring the Tuning Manager server data and the Agent
database on a host on which these products are installed in a Windows environment.
7-b.2
Prerequisites
See the description of restoration in the following manual and confirm that the described
preconditions are satisfied. If you perform restoration when not all the preconditions are satisfied,
you will be unable to restore data normally.
[ manual title]
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
Hitachi Command Suite Tuning Manager Agent Administration Guide
7-b.3
Applicable Versions
7-b.4
Terms
Terms
Folder
Hitachi-StorageCommand-Suite-Common-Component
<Installation-directory>\Base
1
-installation-directory
2
Hitachi-Tuning-Manager-installation-directory
<Installation-directory>\TuningManager
Installation-directory
for Windows Server 2003 x86, and Windows Server 2008 x86:
%SystemDrive%\Program Files\HiCommand
for Windows Server 2003 x64, Windows Server 2008 x64 and Windows
Server 2012:
%SystemDrive%\Program Files (x86)\HiCommand
Agent-installation-directory
<Installation-directory>\TuningManager\jp1pc
394
Platform-Agent-Tuning-Manager-installation-directory
<Installation-directory>\TuningManager\jp1pc
Note: Unless you specify other directories during installation, the above directories are used by
default.
7-b.5
Figure 7-c.7-1 provides an overview of the procedure for restoring the Tuning Manager server data
and Agent database on a host on which these products are installed in a Windows environment.
Start
Suite products
7-b.6(1)
7-b.7
7-b.8
7-b.8(ii)
7-b.9(1)
Stop Agent
7-b.9(2)
7-b.10
7-b.11
7-b.12
7-b.13
End
Figure 7-b.7-1 An overview of the procedure for restoring the Tuning Manager server and Agent databases
395
7-b.6
Command line
cd <Hitachi-Tuning-Manager-installation-directory>\bin\
Output example
KAPM06903-I The service was stopped successfully.
Note: For details about the hcmdsdb command, see the manual.
7-b.7 Restore the definition information files for the Tuning Manager server
Use the Windows COPY command to copy the backed-up Tuning Manager server definition
information files, overwriting the files at the destination. For a list of the Tuning Manager server
definition information files to restore, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
The following shows an example of using the Windows COPY command to restore the definition
information files for the Tuning Manager server:
Command line
COPY d:\backup\HiCommand\TuningManager\jp1pc\jpchosts
< Hitachi-Tuning-Manager-installation-directory >\TuningManager\jp1pc
COPY d:\backup\HiCommand\TuningManager\jp1pc\*.ini
< Hitachi-Tuning-Manager-installation-directory >\TuningManager\jp1pc
396
COPY d:\backup\HiCommand\TuningManager\jp1pc\bin\action\*.ini
< Hitachi-Tuning-Manager-installation-directory >\jp1pc\bin\action
COPY d:\backup\HiCommand\TuningManager\jp1pc\bin\statsvr\*.ini
< Hitachi-Tuning-Manager-installation-directory >\jp1pc\bin\statsvr
COPY d:\backup\HiCommand\TuningManager\conf\user.properties
<Hitachi-Tuning-Manager-installation-directory>\conf
COPY d:\backup\HiCommand\TuningManager\conf\logging.properties
<Hitachi-Tuning-Manager-installation-directory>\conf
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\clator\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\clator
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.DB
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager
10
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.IDX
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager
11
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.DAT
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager
12
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\store\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\store
13
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\store\*.DAT
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\store
14
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr
15
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr\*.DB
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr
16
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr\*.IDX
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr
17
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\trapgen\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\trapgen
18
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr
19
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvrdata\*
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\data
20
COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr\reports\*
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\reports
21
COPY d:\backup\HiCommand\TuningManager\jp1pc\agt0\agent\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\agt0\agent
22
COPY d:\backup\HiCommand\TuningManager\jp1pc\agt0\store\*.ini
397
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\agt0\store
23
COPY d:\backup\HiCommand\TuningManager\system\sysconf\ui.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
24
COPY d:\backup\HiCommand\TuningManager\system\sysconf\core.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
25
COPY d:\backup\HiCommand\TuningManager\system\sysconf\cli.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
26
COPY d:\backup\HiCommand\TuningManager\system\sysconf\common.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
27
COPY d:\backup\HiCommand\TuningManager\system\sysconf\system.logging.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
The following shows an example of using the Windows COPY command to restore the definition
information files for Performance Reporter:
Command line
1 COPY d:\backup\HiCommand\TuningManager\PerformanceReporter\conf\*.*
<Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\conf
Copy the backup of the bookmarks folder for Performance Reporter to the following folder,
overwriting the files at the destination.
#
1
Folder
<Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\bookmarks
Note: The above folder is an example when the "bookmarkRepository" item of the initialization
settings file (config.xml) of Performance Reporter is not specified. Back up Performance Reporter
bookmarks from the folder specified as the "bookmarkRepository" item of the initialization settings
file (config.xml) of Performance Reporter.
398
The following shows an example of using the Windows XCOPY command to copy Performance
Reporter bookmarks, overwriting the files at the destination:
Command line
XCOPY /e /y /I
d:\backup\HiCommand\TuningManager\PerformanceReporter\bookmarks
<Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\bookmarks
7-b.8(ii) Restore the definition information files for Tuning Manager REST Service
(Ver. 8.0 or later)
In version 8.0, if you are using Tuning Manager API, it is necessary to restore the
definition information files for Tuning Manager REST Application Service.
Copy the backed up files (see 7.a.7(ii)) matching the directory structure of the
destination (for restoring).
Command line
cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
jpcstop all
Command line
cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
Output example
399
Note: For details about the jpcresto command, see the manual.
The following shows an example of how to use the Windows "COPY" command to restore the Agent
definition information files.
Note that files #5 and #6 might not exist in certain environments. If these files do not exist, the
"COPY" command will fail. However, the failure of this command does not affect the backup
operation.
Command line
1 COPY d:\backup\HiCommand\TuningManager\jp1pc\xxxx\agent\*.ini
<Agent-installation-directory>\xxxx\agent
2 COPY d:\backup\HiCommand\TuningManager\jp1pc\xxxx\agent\instance-name\*.ini
<Agent-installation-directory>\xxxx\agent\instance-name
3 COPY d:\backup\HiCommand\TuningManager\jp1pc\xxxx\store\*.ini
<Agent-installation-directory>\xxxx\store
4 COPY d:\backup\HiCommand\TuningManager\jp1pc\xxxx\store\instance-name\*.ini
<Agent-installation-directory>\xxxx\store\instance-name
5 COPY d:\backup\HiCommand\TuningManager\jp1pc\agtw\agent\agtw.properties
<Agent-installation-directory>\agtw\agent
6 COPY d:\backup\HiCommand\TuningManager\jp1pc\agtt\agent\jpcapp
<Agent-installation-directory>\agtt\agent
400
Note: xxxx indicates the service key of each Agent. For details on the service keys of each Agent,
see 4.1.5. jpcras command.
7-b.11 Restore the definition information files for HTnM-Agent REST Services (Ver. 8.0 or
later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must restore the definition information files for HTnM-Agent REST Services. Copy the backed
up files (see 7.a.10) matching the directory structure of the destination (for restoring).
7-b.12 Restore the performance data for Tuning Manager API (Ver. 8.0 or later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must restore the performance data for Tuning Manager API. Copy the backed up performance
data (see 7.a.11) matching the directory structure of the destination (for restoring).
[Note]
By editing the property file (apidataglobalconfig.ini or jpcagt.ini) the output destination of the
performance data can be changed. If the output destination for performance data has been changed,
copy the backed up files to the changed output destination of the performance data.
Command Line
cd <Agent-installation-directory>\jp1pc\htnm\bin
Command Line
cd <Agent-installation-directory>\jp1pc\htnm\bin
401
7-c. Backup procedure on a host on which the Tuning Manager server and Agent are installed in
a UNIX environment
7-c.1
Purpose
This section describes the procedure for backing up the Tuning Manager server data and the Agent
database on a host on which these products are installed in a UNIX environment.
7-c.2
Applicable Versions
7-c.3
Terms
Terms
Directory
Hitachi-Storage-Command-Suite-Common-Component-installation-directory
1
[ In Ver.8 or later ]
/opt/HiCommand/Base64
2
Hitachi-Tuning-Manager-installation-directory
/opt/HiCommand/TuningManager
Installation-directory
/opt/HiCommand
Agent-installation-directory
/opt/jp1pc
Platform-Agent-Tuning-Manager-installation-directory
/opt/jp1pc
Note: Unless you specify other directories during installation, the above directories are used by
default.
402
7-c.4
7-c.5(1)
7-c.5(2)
Back up the definition information files for the Tuning Manager server
7-c.6
7-c.7
7-c.7(ii)
7-c.8(1)
Start Agent
7-c.8(2)
7-c.9(1)
Stop Agent
7-c.9(2)
7-c.10
7-c.11
7-c.12
End
Figure 7-c.7-1 An overview of the procedure for backing up the Tuning Manager server and Agent databases
403
7-c.5
Command line
For Solaris:
cd /opt/HiCommand/TuningManager/bin
For Linux :
cd <TuningManager-Installation-directory>/bin
2
./htm-db-status
Output example
KATN01314-I The command htm-db-status will now be executed.
Database Capacity (Used/Total): 15560 / 2048000 kBytes
Area Path:
/TMP/Program Files/HiCommand/TuningManager/database/TuningManager/TM00
KATN01309-I The database status has been displayed.
404
Command line
For Solaris :
cd /opt/HiCommand/Base/bin
For Linux :
cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
[ In Ver.6 to earlier than 8 ]
Note: For details about the hcmdsbackups command, see the manual.
7-c.6
Back up the definition information files for the Tuning Manager server
Use the UNIX cp command to back up the definition information files for the Tuning Manager
server. For a list of the Tuning Manager server definition information files to back up, see the
following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
The following shows an example of using the UNIX cp command to back up the definition
information files for the Tuning Manager server. For this example, the destination folders used by
the cp command must be created in advance.
Command line
1 cp /opt/jp1pc/jpchosts /tmp/backup/opt/jp1pc
2 cp /opt/jp1pc/*.ini /tmp/backup/opt/jp1pc
3 cp /opt/jp1pc/bin/action/*.ini /tmp/backup/opt/jp1pc/bin/action
4 cp /opt/jp1pc/bin/statsvr/*.ini /tmp/backup/opt/jp1pc/bin/statsvr
5 cp /opt/<TuningManager-Installation-directory>/conf/user.properties
/tmp/backup/<TuningManager-Installation-directory>/conf
405
6 cp /opt/<TuningManager-Installation-directory>/conf/logging.properties
/tmp/backup/<TuningManager-Installation-directory>/conf
7 cp /opt/jp1pc/mgr/clator/*.ini /tmp/backup/opt/jp1pc/mgr/clator
8 cp /opt/jp1pc/mgr/manager/*.ini /tmp/backup/opt/jp1pc/mgr/manager
9 cp /opt/jp1pc/mgr/manager/*.DB /tmp/backup/opt/jp1pc/mgr/manager
10 cp /opt/jp1pc/mgr/manager/*.IDX /tmp/backup/opt/jp1pc/mgr/manager
11 cp /opt/jp1pc/mgr/manager/*.DAT /tmp/backup/opt/jp1pc/mgr/manager
12 cp /opt/jp1pc/mgr/store/*.ini /tmp/backup/opt/jp1pc/mgr/store
13 cp /opt/jp1pc/mgr/store/*.DAT /tmp/backup/opt/jp1pc/mgr/store
14 cp /opt/jp1pc/mgr/namesvr/*.ini /tmp/backup/opt/jp1pc/mgr/namesvr
15 cp /opt/jp1pc/mgr/namesvr/*.DB /tmp/backup/opt/jp1pc/mgr/namesvr
16 cp /opt/jp1pc/mgr/namesvr/*.IDX /tmp/backup/opt/jp1pc/mgr/namesvr
17 cp /opt/jp1pc/mgr/trapgen/*.ini /tmp/backup/opt/jp1pc/mgr/trapgen
18 cp /opt/jp1pc/mgr/viewsvr/*.ini /tmp/backup/opt/jp1pc/mgr/viewsvr
19 cp /opt/jp1pc/mgr/viewsvr/data/* /tmp/backup/opt/jp1pc/mgr/viewsvr
20 cp /opt/jp1pc/mgr/viewsvr/reports/* /tmp/backup/opt/jp1pc/mgr/viewsvr
21 cp /opt/jp1pc/agt0/agent/*.ini /tmp/backup/opt/jp1pc/agt0/agent
22 cp /opt/jp1pc/agt0/store/*.ini /tmp/backup/opt/jp1pc/agt0/store
23 cp /opt/<TuningManager-Installation-directory>/system/sysconf/ui.properties
/tmp/backup/<TuningManager-Installation-directory>/system/sysconf
24 cp /opt/<TuningManager-Installation-directory>/system/sysconf/core.properties
/tmp/backup/<TuningManager-Installation-directory>/system/sysconf
25 cp /opt/<TuningManager-Installation-directory>/system/sysconf/cli.properties
/tmp/backup/<TuningManager-Installation-directory>/system/sysconf
26 cp /opt/<TuningManager-Installation-directory>/system/sysconf/common.properties
/tmp/backup/<TuningManager-Installation-directory>/system/sysconf
27 cp /opt/<TuningManager-Installation-directory>/system/sysconf/system.logging.properties
/tmp/backup/<TuningManager-Installation-directory>/system/sysconf
7-c.7
Use the UNIX cp command to back up the definition information files for Performance Reporter.
For a list of the Performance Reporter definition information files to back up, see the following
manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
406
The following shows an example of using the UNIX cp command to back up the definition
information files for Performance Reporter. For this example, the destination folders used by the
cp command must be created in advance.
Command line
1 For Solaris :
cp /opt/HiCommand/TuningManager/PerformanceReporter/conf/*.* /tmp/backup/PerformanceReporter/conf
For Linux :
cp <TuningManager-Installation-directory>/PerformanceReporter/conf/*.* /tmp/backup/PerformanceReporter/conf
Back up the Performance Reporter bookmarks stored in the following folder, by using the UNIX
cp command to copy the folder in its entirety.
Directory
1 For Solaris :
/opt/HiCommand/TuningManager/PerformanceReporter/bookmarks
For Linux :
<TuningManager-Installation-directory>/PerformanceReporter/bookmarks
Note: The above directory is an example when the "bookmarkRepository" item of the initialization
settings file (config.xml) of Performance Reporter is not specified. Back up Performance Reporter
bookmarks from the directory specified as the "bookmarkRepository" item of the initialization
settings file (config.xml) of Performance Reporter.
The following shows an example of using the UNIX cp command to back up Performance
Reporter bookmarks:
Command line
1 For Solaris :
cp -r /opt/HiCommand/TuningManager/PerformanceReporter/bookmarks
/tmp/backup/opt/HiCommand/TuningManager/PerformanceReporter
For Linux :
cp -r <TuningManager-Installation-directory>/PerformanceReporter/bookmarks
/tmp/backup<TuningManager-Installation-directory>/PerformanceReporter
7-c.7(ii) Back up the definition information files for Tuning Manager REST Application Service
(Ver.8.0 or later)
In version 8.0.0 or later, if you are using Tuning Manager API, backup of definition
information files for Tuning Manager REST Application Service are required. Back up
407
procedure is the same as (7-a.7(ii)). When using copy command of OS for copying,
execute the copy command corresponding to each platform.
7-c.8
Only perform this procedure for an Agent for which the data storage format is Store database. This
procedure is not necessary on an Agent that is operated with Hybrid Store.
(1) Start Agent.
Execute the commands indicated below.
#
Command line
cd /opt/jp1pc/tools
./jpcstart all
Command line
cd /opt/jp1pc/tools
Note:
If you back up multiple databases to the same specified directory, the data that is backed up
might be inconsistent. Make sure to change the directory each time you perform the backup
operation.
Command line
cd /opt/jp1pc/tools
mkdir /tmp/backup/DS1RAID[host01]
408
Output example
KAVE06000-I Backup processing of the Store database terminated normally. (service= DS1RAID[host01])
Note: For details about the jpcctrl backup command, see the manual.
7-c.9
Only perform this procedure for an Agent for which the data storage format is Store database. This
procedure is not necessary on an Agent that is operated with Hybrid Store.
(1) Stop Agent.
Execute the commands indicated below.
#
Command line
cd /opt/jp1pc/tools
./jpcstop all
The following shows an example of using the Unix cp command to back up the definition
information files for Agent. For this example, the destination folders used by the cp command
must be created in advance.
Note that file #8 might not exist in certain environments. If this file does not exist, the "cp"
command will fail. However, the failure of this command does not affect the backup operation.
Command line
1 cp /opt/jp1pc/xxxx/agent/*.ini /tmp/backup/opt/jp1pc/xxxx/agent
2 cp /opt/jp1pc/xxxx/agent/instance-name/*.ini /tmp/backup/opt/jp1pc/xxxx/agent/instance-name
3 cp /opt/jp1pc/xxxx/store/*.ini /tmp/backup/opt/jp1pc/xxxx/store
4 cp /opt/jp1pc/xxxx/store/instance-name/*.ini /tmp/backup/opt/jp1pc/xxxx/store/instance-name
5 cp /opt/jp1pc/agtu/agent/jpcapp /tmp/backup/opt/jp1pc/agtu/agent
6 cp /opt/jp1pc/agtu/agent/evfile /tmp/backup/opt/jp1pc/agtu/agent
7 cp /opt/jp1pc/agtu/agent/wgfile /tmp/backup/opt/jp1pc/agtu/agent
8 cp /opt/jp1pc/agtt/agent/jpcapp /tmp/backup/opt/jp1pc/agtt/agent
409
Note: xxxx indicates the service key of each Agent. For details on the service keys of each Agent,
see 4.1.5. jpcras command.
7-c.10 Back up the definition information files for HTnM-Agent REST Services (Ver.8.0 or
later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must back up the definition information file for HTnM-Agent REST Services. Back up
procedure is the same as (7-a.10). When using copy command of OS for copying, execute
the copy command corresponding to each platform.
7-c.11 Back up the performance data for Tuning Manager API (Ver.8.0 or later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must back up the performance data for Tuning Manager API. Back up procedure is the same
as (7-a.11). When using copy command of OS for copying, execute the copy command
corresponding to each platform.
The following table lists execution examples of the htmhsbackup command in a UNIX
environment.
#
Command Line
cd /opt/jp1pc/htnm/bin
mkdir /tmp/RAID_backup
410
7-d. Restore procedure on a host on which the Tuning Manager server and Agent are installed
in a UNIX environment
7-d.1 Purpose
This section describes the procedure for restoring the Tuning Manager server data and the Agent
database on a host on which these products are installed in a UNIX environment.
7-d.2 Prerequisites
See the description of restoration in the following manual, and confirm that the described
preconditions are satisfied. If you perform restoration when not all the preconditions are satisfied,
you will be unable to restore data normally.
[manual title]
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
Hitachi Command Suite Tuning Manager Agent Administration Guide
7-d.4 Terms
The following terms are used in this section.
#
Terms
Directory
Hitachi-Storage-Command-Suite-Common-Component-installation-directory
1
[ In Ver.8 or later ]
/opt/HiCommand/Base64
2
Hitachi-Tuning-Manager-installation-directory
/opt/HiCommand/TuningManager
Installation-directory
/opt/HiCommand
Agent-installation-directory
/opt/Hitachi/jp1pc
Platform-Agent-Tuning-Manager-installation-directory
/opt/Hitachi/jp1pc
Note: Unless you specify other directories during installation, the above directories are
411
used by default.
7-d.5
Figure 7-d.7-1 provides an overview of the procedure for restoring the Tuning Manager server data
and Agent database on a host on which these products are installed in a UNIX environment.
Start
Suite products
7-d.6(1)
7-d.7
7-d.8
7-d.8(ii)
Stop Agent
7-d.9(1)
7-d.9(2)
7-d.10
7-d.11
7-d.12
7-d.13
End
Figure 7-d.7-1 An overview of the procedure for restoring the Tuning Manager server and Agent databases
412
7-d.6
Command line
For Solaris :
cd /opt/HiCommand/Base/bin
For Linux :
cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
Output example
KAPM06903-I The service was stopped successfully.
Note: For details about the hcmdsdb command, see the manual.
7-d.7
Restore the definition information files for the Tuning Manager server
Use the UNIX cp command to copy the backed-up Tuning Manager server definition information
files, overwriting the files at the destination. For a list of the Tuning Manager server definition
information files to restore, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
The following shows an example of using the UNIX cp command to restore the definition
information files for the Tuning Manager server:
Command line
cp /tmp/backup/opt/jp1pc/jpchosts /opt/jp1pc
cp /tmp/backup/opt/jp1pc/*.ini /opt/jp1pc
413
cp /tmp/backup/opt/jp1pc/bin/action/*.ini /opt/jp1pc/bin/action
cp /tmp/backup/opt/jp1pc/bin/statsvr/*.ini /opt/jp1pc/bin/statsvr
cp /tmp/backup<TuningManager-Installation-directory>/conf/user.properties
<TuningManager-Installation-directory>/conf
cp /tmp/backup<TuningManager-Installation-directory>/conf/logging.properties
<TuningManager-Installation-directory>/conf
cp /tmp/backup/opt/jp1pc/mgr/clator/*.ini /opt/jp1pc/mgr/clator
cp /tmp/backup/opt/jp1pc/mgr/manager/*.ini /opt/jp1pc/mgr/manager
cp /tmp/backup/opt/jp1pc/mgr/manager/*.DB /opt/jp1pc/mgr/manager
10
cp /tmp/backup/opt/jp1pc/mgr/manager/*.IDX /opt/jp1pc/mgr/manager
11
cp /tmp/backup/opt/jp1pc/mgr/manager/*.DAT /opt/jp1pc/mgr/manager
12
cp /tmp/backup/opt/jp1pc/mgr/store/*.ini /opt/jp1pc/mgr/store
13
cp /tmp/backup/opt/jp1pc/mgr/store/*.DAT /opt/jp1pc/mgr/store
14
cp /tmp/backup/opt/jp1pc/mgr/namesvr/*.ini /opt/jp1pc/mgr/namesvr
15
cp /tmp/backup/opt/jp1pc/mgr/namesvr/*.DB /opt/jp1pc/mgr/namesvr
16
cp /tmp/backup/opt/jp1pc/mgr/namesvr/*.IDX /opt/jp1pc/mgr/namesvr
17
cp /tmp/backup/opt/jp1pc/mgr/trapgen/*.ini /opt/jp1pc/mgr/trapgen
18
cp /tmp/backup/opt/jp1pc/mgr/viewsvr/*.ini /opt/jp1pc/mgr/viewsvr
19
cp /tmp/backup/opt/jp1pc/mgr/viewsvr/data/* /opt/jp1pc/mgr/viewsvr/data
20
cp /tmp/backup/opt/jp1pc/mgr/viewsvr/reports/* /opt/jp1pc/mgr/viewsvr/reports
21
cp /tmp/backup/opt/jp1pc/agt0/agent/*.ini /opt/jp1pc/agt0/agent
22
cp /tmp/backup/opt/jp1pc/agt0/store/*.ini /opt/jp1pc/agt0/store
23
cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/ui.properties
<TuningManager-Installation-directory>/system/sysconf
24
cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/core.properties
<TuningManager-Installation-directory>/system/sysconf
25
cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/cli.properties
<TuningManager-Installation-directory>/system/sysconf
26
cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/common.properties
<TuningManager-Installation-directory>/system/sysconf
27
cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/system.logging.properties
<TuningManager-Installation-directory>/system/sysconf
7-d.8
Use the UNIX cp command to copy the backed-up Performance Reporter definition information
files, overwriting the files at the destination. For a list of the Performance Reporter definition
information files to restore, see the following manual:
- In Ver.6
414
The following shows an example of using the UNIX cp command to restore the definition
information files for Performance Reporter:
Command line
1 For Solaris :
cp /tmp/backup/opt/HiCommand/TuningManager/PerformanceReporter/conf/*.*
/opt/HiCommand/TuningManager/PerformanceReporter/conf
For Linux :
cp /tmp/backup<TuningManager-Installation-directory>/PerformanceReporter/conf/*.*
<TuningManager-Installation-directory>/PerformanceReporter/conf
Copy the backup of the bookmarks folder for Performance Reporter to the following folder,
overwriting the files at the destination.
Directory
1 For Solaris :
/opt/HiCommand/TuningManager/PerformanceReporter/bookmarks
For Linux :
<TuningManager-Installation-directory>/PerformanceReporter/bookmarks
Note: The above directory is an example when the "bookmarkRepository" item of the
initialization settings file (config.xml) of Performance Reporter is not specified. Back up
Performance
Reporter
bookmarks
from
the
directory
specified
as
the
Command line
1 For Solaris :
cp -r /tmp/backup/opt/HiCommand/TuningManager/PerformanceReporter/bookmarks
/opt/HiCommand/TuningManager/PerformanceReporter
For Linux :
415
cp -r /tmp/backup<TuningManager-Installation-directory>/PerformanceReporter/bookmarks
<TuningManager-Installation-directory>/PerformanceReporter
7-d.8(ii) Restore the definition information files for Tuning Manager REST Service
(Ver. 8.0 or later)
In version 8.0, if you are using Tuning Manager API, it is necessary to restore the
definition information files for Tuning Manager REST Application Service. Restore
procedure is the same as (7-b.8(ii)). When using copy command of OS for copying,
execute the copy command corresponding to each platform.
Command line
cd /opt/jp1pc/tools
./jpcstop all
Command line
cd /opt/jp1pc/tools
Output example
KAVE06006-I Store Restore processing of the Store database terminated normally
Note: For details about the jpcresto command, see the manual.
416
The following shows an example of using the Unix cp command to restore the definition
information files for Agent:
Command line
1 cp /tmp/backup/opt/jp1pc/xxxx/agent/*.ini /opt/jp1pc/xxxx/agent
2 cp /tmp/backup/opt/jp1pc/xxxx/agent/instance-name/*.ini /opt/jp1pc/xxxx/agent/instance-name
3 cp /tmp/backup/opt/jp1pc/xxxx/store/*.ini /opt/jp1pc/xxxx/store
4 cp /tmp/backup/opt/jp1pc/xxxx/store/instance-name/*.ini /opt/jp1pc/xxxx/store/instance-name
5 cp /tmp/backup/opt/jp1pc/agtu/agent/jpcapp /opt/jp1pc/agtu/agent
6 cp /tmp/backup/opt/jp1pc/agtu/agent/evfile /opt/jp1pc/agtu/agent
7 cp /tmp/backup/opt/jp1pc/agtu/agent/wgfile /opt/jp1pc/agtu/agent
8 cp /tmp/backup/opt/jp1pc/agtw/agent/agtw.properties /opt/jp1pc/agtw/agent
Note: xxxx indicates the service key of each Agent. For details on the service keys of each Agent,
see 4.1.5. jpcras command.
7-d.11 Restore the definition information files for HTnM-Agent REST Services
(Ver. 8.0 or later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must restore the definition information file for HTnM-Agent REST Services. Restore
procedure is the same as (7-b.11). When using copy command of OS for copying, execute
the copy command corresponding to each platform.
417
7-d.12 Restore the performance data for Tuning Manager API (Ver. 8.0 or later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must restore the performance data for Tuning Manager API. Restore procedure is the same
as (7-b.12). When using copy command of OS for copying, execute the copy command
corresponding to each platform.
Command Line
cd /opt/jp1pc/htnm/bin
Command Line
cd /opt/jp1pc/htnm/bin
418
Appendix 8 For the version 7.0 or later, substitute the following terms as
indicated
In Ver.7 or later, when reading, replace the terms in the text according to the following table.
No.
In Ver.6 or earlier
In Ver.7 or later
1.
. (Abbreviation : HSCS)
2.
3.
(Abbreviation : HCS)
Hitachi Device Manager
Storage System
.
4.
3 Array Group
Parity Group
.
5.
Host Group
. (Abbreviation : HSD)
6.
Array Configuration
419
OS
Owner
Group
Solaris
root
sys or root
Linux
root
root
The permission of file and directory that is placed or generated below /opt/jp1pc follows the
Agent policy.
OS
Owner
Group
Solaris
root
sys
Linux
root
sys#1
root#2
AIX
root
system
HP-UX
root
sys
#1: Files and directories allocated when Agent is installed, and some files and directories created
when the instances are created
#2: Files and directories created after Agent is installed, except those mentioned in #1 above
File and directory access permission policy
- Permissions for files and directories placed or generated by HTnM Agent
Only the root user is given write permission.
- HTnM Agent-supplied commands
About execution permission of commands, see the manual.
420
10-a.1 Cases
Case 1:
Initialization of an HTnM server fails with the error "KATN10009-E Startup confirmation of a
component related to Main Console has failed. Check the component logs and, if an error
occurred, remove the cause of the error. (Component name = Performance Reporter)".
Case 2:
Installation of an HTnM for Server System in an environment where HTnM for RAID Agent is
already installed fails with "abnormally ended error code : 82".
Case 3:
Uninstallation of HTnM for RAID Agent fails.
Case 4:
Restart of Agent (jpcstop/jpcstart all) fails.
10-a.2 Causes
Case 1 cause:
The cause of case 1 is that there is a zero-byte size file named "hcmdssrv" (without an
extension) in the same folder as "hcmdssrv.exe". Due to the existence of this file, execution of
the "hcmdssrv" command, which is called internally to check startup of Performance Reporter,
failed.
The log htmTraceX.log shows that CreateProcess() failed with error code 193. This error code
is equivalent to the Windows System Error Code ERROR_BAD_EXE_FORMAT, and indicates
an invalid Win32 application.
[htmTraceX.log]
nnnn 20YY/MM/DD hh:mm:ss.xxx
HTnM
com.Hitachi.soft.HiCommand.TM.mc.core.init.InitialUtility#exec()
Caused
by:
EC
java.io.IOException:
at
com.Hitachi.soft.HiCommand.TM.mc.util.process.ProcessRunner.innerExecute(ProcessRunner.java:267)
at
com.Hitachi.soft.HiCommand.TM.mc.util.process.ProcessRunner.execute(ProcessRunner.java:207)
at
com.Hitachi.soft.HiCommand.TM.mc.core.init.ExternalCommand.exec(ExternalCommand.java:72)
at
com.Hitachi.soft.HiCommand.TM.mc.core.init.InitialThread.initializationOf_20_Percent(InitialThread.java:391)
421
at com.Hitachi.soft.HiCommand.TM.mc.core.init.InitialThread.run(InitialThread.java:90)
Cause of cases 2 to 4:
The cause of cases 2 to 4 is that there is a zero-byte size file named "jpcctrl" (without an
extension) in the same folder as "jpcctrl.exe". Due to the existence of this file, execution of the
"jpcctrl" command, which is called internally in each of the cases, failed.
For case 2, msglogX shows that CreateProcess() failed with the error "CreateProcess() error
occurred."
For cases 3 and 4, jpclogX shows that execution of the command called internally in each of the
cases failed with the error "KAVE05091-E An internal command cannot be executed.
10-a.3 Solutions
For all of the above cases, the error can be fixed by deleting the file with the same name as the
command (the file without an extension).
For case 1, you will need to restart the HTnM service after deleting the file.
10-b Cases in which HTnM did not operate correctly due to an IPv6 loopback
address(ealier than 7.4.1)
In some cases, HTnM did not operate correctly because it was affected by a loopback address
specified as the IPv6 address for the HTnM host.
10-b.1 Cases
Case 1:
Even if HTnM - Agent for Server System has been installed, the HTnM server recognized only
Agentless mode.
Case 2:
Storage being monitored by HTnM - Agent for RAID was not displayed in Main Console.
Case 3:
Host being monitored by HTnM - Agent for Server System was not displayed in Main Console.
10-b.2 Causes
The cause of cases 1, 2 and 3 is that the IPv6 address set on the HTnM host is a loopback
address.
If IPv6 is enabled in HTnM, IPv6 is preferentially used.
Therefore, when the HTnM server and HTnM - Agent are installed on different hosts and a
loopback address is acquired as the IPv6 address for a host, the HTnM server and HTnM Agent attempt to communicate with each other by using the acquired loopback address.
However, because the loopback address is used, communication is not normal and a
communication error occurs.
For the HTnM server, cases 1, 2 and 3 occur.
422
For HTnM - Agent, the following log entry indicating a communication error is output to
msglog:
KAVE00106-E An error occurred in the network. (rc=-6)
10-b.3 Solutions
The problem can be corrected by using either of the following methods.
(1) Setting an IPv6 address
Set a global unicast address for the HTnM server and each HTnM - Agent host. In addition,
use the hosts file or similar means to specify unique host names for the HTnM server and
each HTnM - Agent.
If an alias is set for a host name, also see Monitoring an Agentless host that uses an alias in
the Tuning Manager Server Administration Guide.
(2) Disabling IPv6
Use the following command to disable IPv6 so that IPv4 is used as the communication
protocol between the HTnM server and each HTnM - Agent:
- jpcnsconfig ipv6 disable
For details about how to use the command, see 7.1. Disabling IPv6 (Ver. 6 or later) in this
document.
10-c The device information for an instance of RAID Map Agent started from a job
management product cannot be obtained
In AIX, in which an instance of RAID Map Agent is started from the job management product Job
Management Partner 1/Automatic Job Management System 3, when an attempt is made to obtain the
device information from the agent, the attempt fails because the environment variable is incorrect.
This problem can be located by using the corresponding AIX command to check whether the
environment variable for the process is correctly specified.
10-c.1 Problem
An attempt to obtain device information from RAID Map Agent fails, and the KAVF19664-E
message is output.
- KAVF19664-E message
[Message details]
KAVF19664-E FS information cannot be obtained. An internal command ended abnormally.
(rc=2)
[Output destination]
Common message log (jpclog)
10-c.2 Cause
This problem occurs if the environment variable ODMDIR is not specified when RAID Map
423
[Command used]
ps ewwwg
[Output example]
14418032
0:00
jpcagte
-d
/opt/jp1pc/agte/agent
_=/opt/jp1pc/tools/jpcstart
EA2_0050_BAT_MAX_FILE_SIZE=24000000000
EA2_0010_HULCLUSTEROBS_TIMEOUT=10
LANG=C
(Omitted)
AJSNETNAME=/HOUSH
=> The line with the process jpcagte does not contain the environment variable ODMDIR.
[Isolation result]
The line with the process jpcagte is supposed to contain the environment variable ODMDIR,
but in the preceding example of command output it is omitted. This indicates that the
problem will occur.
10-c.4 Solution
If the environment variable ODMDIR is not loaded into the process jpcagte as previously
described, configure the job management product to inherit /etc/environment.
- KFPS01892-E Message
[Message]
KFPS01892-E pd_max_users invalid; stops unit startup. server
ID=sds01, old value=84, new value=96
[Log output destination]
424
pdlog
10-d.2 Causes
The HCS service is forcibly terminated when establishing a cluster environment because the
cluster software is attempting to start or stop the HCS service set in the standby system under
the following condition:
- HDvM and HTnM are installed on the executing node, but only HDvM is installed on the
standby node (HTnM is not installed on the standby node).
Under the above condition, if the HTnM is installed on the standby node, the parameter related
to HiRDB memory (pd_max_users) is changed (the message shown above is issued),
leading to a difference between the parameters of the executing node and the standby node.
This causes the HiRDB service to become unable to start.
10-d.3 Solutions
To recover HiRDB:
(1) Take the HCS service offline from the cluster software.
425
(7) Change the HiRDB setting changed in (3) back to its original value.
Change line 13 of the following file as shown below:
<Common-Component-installation-directory>\HDB\CONF\pdsys
from set pd_max_users = 84
to set pd_max_users = 96
(8) Change HiRDB to the online status from the cluster software.
(9) Confirm whether HiRDB is online (the status has recovered) from the cluster software.
- KAVE05033-E Message
[Message]
KAVE05033-E A service could not start. (service=Agent for UNIX,
rc=-5)
[Log output destination]
jpclog
10-e.2 Causes
An error like above is caused by the difference in the number of bits between AIX (64-bit) and
Agent for Platform (32-bit). Such a difference in the number of bits seems to result from a
change in the number of bits between the 32-bit and 64-bit versions of AIX.
426
Note: Only a 64-bit version of AIX is available for AIX versions later than 5.3; thus no errors as
described in this section occur.
: aix4.3.3.0 (32-bit)
Target OS Name
: AIX
Target OS Release
: 5.3.0.0 (64-bit)
The Agent for Platform module is 32-bit, while the AIX kernel is 64-bit. this difference
is what causes the problem.
10-e.4 Solutions
If you have changed the number of bits in the kernel, take either of the following
countermeasures:
(1) Reinstall Agent for Platform.
If you have any data to be retained, make a backup of that data before reinstalling Agent for
Platform, and then restore the data after the reinstallation.
(2) Change the number of bits of the AIX kernel to its previous configuration.
427
-Output example
428
/opt/HiCommand/Base/jdk/bin/java
-Djava.vendor="Sun
Microsystems
Inc."
-jar
/tmp/tzupdater.jar -V
tzupdater version 1.3.29-b01
[ In Ver.8 or later ]
For Windows
"C:\Program
-Djava.vendor="Sun
Files\HiCommand\Base64\uCPSB\jdk\bin\java"
Microsystems
Inc."
-jar
"C:\Program
Files\HiCommand\Base64\tzupdater.jar" -V
tzupdater version 1.3.62-b01
Embedded time zone data version: tzdata2013i ------ Updated tzdata version
For Linux
% /opt/HiCommand/Base64/uCPSB/jdk/bin/java -Djava.vendor="Sun Microsystems
Inc." -jar /tmp/tzupdater.jar V
tzupdater version 1.3.62-b01
For Linux
[ In Ver.6 to earlier than 8 ]
<Suite Install-dir>/jdk/bin/java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar -v -u
[ In Ver.8 or later ]
<Suite Install-dir>/uCPSB/jdk/bin/java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar
-v -u
-Output example
[ In Ver.6 to earlier than 8 ]
For Windows
"C:\Program Files\HiCommand\Base\jdk\bin\java" -Djava.vendor="Sun Microsystems Inc." -jar
"C:\Program Files\HiCommand\Base\tzupdater.jar" -v -u
java.home: C:\Program Files\HiCommand\Base\jdk\jre ------JDK to be applied
java.vendor: Sun Microsystems Inc.
java.version: 1.5.0_11
------JDK version
/opt/HiCommand/Base/jdk/bin/java
-Djava.vendor="Sun
Microsystems
Inc."
-jar
"/tmp/tzupdater.jar" -v -u
java.home: /opt/HiCommand/Base/jdk/jre ------JDK to be applied
java.vendor: Sun Microsystems Inc.
java.version: 1.5.0_05
------JDK version
the
new
time
zone
data...
Extracting
files...
Creating:
/opt/HiCommand/Base/jdk/jre/lib/tz.tmp/: /pkg_resolve.sh
done.
Updating package HBASE with timezone base directory /opt/HiCommand/Base/jdk/jre/lib/zi
(update time is variable, but can take several minutes)
Removing previous package entries...
Installing new package entries...
Completed resolving Solaris package information.
done.
430
-Djava.vendor="Sun
Microsystems
Inc."
-jar
"/tmp/tzupdater.jar" -v -u
java.home: /opt/HiCommand/Base/jdk/jre ------JDK to be applied
java.vendor: Sun Microsystems Inc.
java.version: 1.5.0_05
------JDK version
[ In Ver.8 or later ]
For Windows
"C:\Program
-Djava.vendor="Sun
Files\HiCommand\Base64\uCPSB\jdk\bin\java"
Microsystems
Inc."
-jar
"C:\Program
Files\HiCommand\Base64\tzupdater.jar" -v -u
java.home: C:\Program Files\HiCommand\Base64\uCPSB\jdk\jre ------JDK to be
applied
java.vendor: Sun Microsystems Inc.
java.version: 1.5.0_11
------JDK version
------JDK to be applied
java.version: 1.5.0_05
------JDK version
11-c Notes
(1) Before applying tzupdater, stop the HCS service.
(2) When using tzupdater, specify the full path for the java command to be executed. Also, specify
java command options in the same order as given above, in 11-b(1) or 11-b(2).
(3) If HCS is updated or a service pack is applied to it after tzupdater is applied, tzdata may be reset
to the version before tzupdater was applied. After updating HCS or applying a service pack,
check the tzdata version and update tzdata if necessary.
432
Case 2:
KAVJK0401-E
jpcrpt
-y
-input
E:\Monthly_Stats\Graphical\Input_Files\PP2USP01O_LDev.xml
-o
E:\Monthly_Stats\Graphical\Results\PP2USP01O\PP2USP01O_LDev_Response:
Memory has become insufficient.
A server memory shortage occurred.
Stop unnecessary applications and close windows to increase the available memory, and then retry.
12-a.2 Causes
Cause of case 1:
The cause of case 1 is that many records are to be output, but there is not enough memory in
View Server to output a report. In the message shown in Case 1, "ViewServer error code:
-2001" indicates that View Server memory is insufficient. For details, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
Cause of case 2:
The cause of case 2 is that many records are to be output, but there is not enough memory in PR
to output a report. You can also execute the jpcrpt command to display the log
jpcrpt_logX.log, where you can check whether memory is insufficient in PR.
433
HTM-PR
EC
EC
HTM-PR
HTM-PR
Memory
has
become insufficient. A server memory shortage occurred. Stop unnecessary applications and close windows to
increase the available memory, and then retry.
12-a.3 Solutions
(1) Enable split transmission mode for a CSV-format report
When a report is output by executing the jpcrpt command with split transmission mode
enabled, PR can receive split report data from View Server. This might prevent a memory heap
shortage in View Server or PR, but it cannot be used for output of an HTML report.
To set split transmission mode, set blockTransferMode in the PR initialization settings file
(config.xml) to true. For details, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
(3) Increasing the Java heap size used by the jpcrpt command
You can specify the maximum Java heap size that the jpcrpt command can use with the mx
434
option of the jpcrpt command (applicable versions: 7.3.0 and later). For details, see the
following manual:
- In Ver.6
Hitachi Tuning Manager Software Command Line Interface Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software CLI User Guide
- In Ver.7.1 to earlier than 8.0
Hitachi Command Suite Tuning Manager Software CLI Reference Guide
- In Ver.8
Hitachi Command Suite Tuning Manager CLI Reference Guide
If the problem cannot be avoided by performing (1),(2) and (3) above when you use the HTML
format, consider outputting the data to a CSV file. Also consider changing the report definition so
that the number of records output at one time is restricted based on a period or metric.
12-b Actions to be taken when Main Console terminates abnormally during polling
12-b.1 Cases
When an attempt is made to log in to HTnM, the message HTTP 500 Internal server
Error appears in the browser, and login is impossible.
12-b.2 Causes
The cause of this problem is that Main Console terminates abnormally because the memory
heap in Main Console was insufficient during polling. If you check the javalog for Main
Console, you will see that a Java memory shortage has occurred.
[ In Ver.6 to earlier than 8 ]
[HCS-installation-directory\Base\CC\web\containers\TuningManager\logs\javalogXX.log]
[ In Ver.8 or later ]
[HCS-installation-directory\Base64\CC\web\containers\TuningManager\logs\javalogXX.log]
[VGC]<Wed Jun 30 12:05:07.455 2010>[Full GC 631730K->631705K(633536K), 2.8359948 secs][DefNew::Eden:
174783K->174783K(174784K)][DefNew::Survivor:
436928K->436928K(436928K)][Perm:
20018K->19993K(21824K)][Tenured:
55905K->55884K(65536K)][cause:ObjAllocFail][User:
2.8281250
12-b.3 Solutions
To prevent a memory shortage in Main Console during polling, you need to reduce the polling
load.
There are three ways to reduce the polling load:
(1) Reduce the period of time for collecting past data during polling.
435
436
13-a Identifying the target for which the KAVE00213-W message is output
Identify the Agent instance and record type for which the KAVE00213-W message was generated
in the common message log (jpclog).
Note that if the KAVE00213-W message is output only temporarily for the same Agent instance,
you do not have to take any action.
1169 KAVE00213-W
Collection of the performance data will be skipped because collection processing was delayed.
(skipped time=2012/04/18 17:01:00, scheduled time=2012/04/18 17:02:00, record=PI_PI,
type=historical)
Agent Collector service, you can identify the Agent instance in question by checking the
storage path of the msglogX. For details about msglog, see the Log Information Analysis
Procedure Manual.
Note that although the PID is changed each time the Agent is restarted, if the Agent was not
restarted from the moment the problem occurred to the moment the log was recorded, you can
also identify the Agent in the jpcctrl.log.
13-b Guide for specifying a value for the Collection Interval for records of the
PI record type
Set the Collection Intervals using the recommended values described in this section as a guide.
438
Note that you can check the port count of the host or storage that is connected to a switch within
the fabric to which the monitoring target switch belongs in msglog.
msglogX
2012/07/09
14:02:17
jpcagtw
00012964
00002212
saC_CimData.cpp
0264
Return
the
java
Brocade_SANActiveConnection
McDATA_SwitchActiveConnection
CISCO_ActiveConnection
Cisco(Seed Switch)
439
(*1)/(*2)
connected
1
(*1)
Brocade_SwitchFCPortOfEthernetPort
Brocade_SwitchFCPortSCSIProtocolEndPoint
McDATA_FabricPortGroup
CISCO_LogicalForPhysicalComputerSystem
Cisco(Seed Switch)
CISCO_DeviceSAPImplementation
saC_SwitchAccessorDCFM
(*2)
saC_SwitchAccessorBR
saC_SwitchAccessorMC
saC_SwitchAccessorDCNM
10
Cisco(Seed Switch)
saC_SwitchAccessorCI
440
Table14.a.1-1 Service IDs and service keys specified when performing backup and restore
operations
#
Product
Service ID
Service key
Collection Manager
PSxxxx
mgr
RAID Agent
DSxxxx
agtd
ESxxxx
agte
EAP Agent
MSxxxx
agtm
NAS Agent
NSxxxx
agtn
Oracle Agent
OSxxxx
agto
SQL Agent
QSxxxx
agtq
DB2 Agent
RSxxxx
agtr
TSxxxx
agtt
USxxxx
agtu
11 Switch Agent
WSxxxx
agtw
12 Exchange Agent
ZSxxxx
agtz
13 Action Handler
act
14 Status Server
stat
0Sxxxx
agt0
441
Appendix 15. Handling cases in which the host name was incorrectly changed
(in V7.6.1 or later)
15-a Overview
In versions earlier than 7.6.1, if the host name is changed without following the correct procedure
(*) and then HTnM is activated, data corruption occurs.
This problem does not occur in 7.6.1 and later versions. In these versions, if the host name is
changed by following the wrong procedure, services related to HTnM will not start. To restart these
services, you must restore the old host name, and then re-change the host name by following the
correct procedure. If you cannot restore the old host name, take action as described in 15-b.
You can use RAS information to check whether the host name was changed in the correct manner.
This procedure is explained in 15-c.
(*) See the section Changing a host name after starting operations in the following manual:
- In Ver.6
Hitachi Tuning Manager Software Installation Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Installation Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Installation Guide
15-b Action to take if you cannot restore the old host name
This section describes the action to be taken only if you cannot restore the old host name.
The action differs depending on the host:
(1) If the name of an HTnM server host was changed, see 15-b.1.
(2) If the name of an HTnM agent host was changed, see 15-b.2.
15-b.1 Action to take if the name of an HTnM server host was changed
(1) Change the Common Component settings as described in the section Changing the settings of
the Hitachi Command Suite Common Component database of the following manual:
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
Stop all HTnM agents programs and services on the HTnM agents host connected to the HTnM
server. Use the jpcstop command to Stop the services.
442
If the HTnM agents connected to the HTnM server is operating in a logical host environment,
use the cluster software to Stop the HTnM agents services that are running.
Stop all programs and services of Hitachi Command Suite products on the HTnM server host.
Use the hcmdssrv command and jpcstop command to Stop the services.
If the KAVE05217-E message is output and the services fail to Stop when the jpcstop command
is executed, edit the jpchosts file so that the old host name can be resolved, and then execute the
command again. Delete these settings after the services are Stopped.
Follow the procedure below to check the currently configured physical host name on the
HTnM server host.
a)
Use the following command to check the monitoring host name acquisition method:
jpcconf host hostmode -display
b)
Based on the monitoring host name acquisition method confirmed in a) above, use the
appropriate command below to check the physical host name of the OS.
1.
2.
(5) Change the monitoring host name of the HTnM server host.
On the HTnM server host, execute the jpcconf host hostname command to change the
monitoring host name. The command examples shown below change the physical host name to
"hostB".
1.
In Windows:
jpcconf host hostname -newhost hostB -d d:\backup -dbconvert convert
2.
In UNIX:
jpcconf host hostname -newhost hostB -d /var/tmp/backup -dbconvert convert
(6) Change the jpchosts file, hosts file, and DNS settings as necessary, so that the name of the
In a configuration in which an HTnM agent is installed on an HTnM server host, you might
need to perform HTnM agent-specific procedures.
For details about HTnM agent-specific procedures, see Agent-specific procedures when
changing monitoring host name in the Hitachi Tuning Manager software Installation Guide.
443
Start the programs and services of Hitachi Command Suite products on the HTnM server host.
Use the hcmdssrv command and jpcstop command to Stop the services.
Use Performance Reporter to remove the alarm table mapping for the health check agent whose
service ID includes the old host name.
Use Performance Reporter to remove the alarm table mapping for the HTnM agent whose
service ID includes the old host name and that is installed on the same host as the HTnM server.
(11) Delete the service information from the HTnM server host.
If service information that includes the old host name remains, delete the service information by
using the following procedure:
1.
Execute the jpcctrl list command to search for the remaining service information.
jpcctrl list "*" host=< the old host name >
jpcctrl list "*" host=< the changed host name >
Check the output of the above two commands. The entries to be deleted are those that have
the old host name in the Service ID column.
Note:
In some cases, the jpcctrl list command might not display services associated with the old
host name. In such cases, you can delete the service information by performing step 2
below.
2.
If the jpcctrl list "*" command results include service information with service IDs that
include the old host name in the Service ID column and with the changed host name in
Host Name, specify the host names and execute the command as follows:
jpcctrl delete "???< the old host name >" host=< the changed host name >
jpcctrl delete "*[< the old host name >]" host=< the changed host name >
If the KAVE05233-W message is output and the service information fails to delete when
the command is executed, specify the force option and execute the command again.
444
jpcctrl delete "???< the old host name >" host=< the changed host name > -force
jpcctrl delete "*[< the old host name >]" host=< the changed host name > -force
3.
Execute the jpcctrl list command to confirm that the service information was correctly
deleted.
jpcctrl list "*" host=< the old host name >
jpcctrl list "*" host=< the changed host name >
Check the output of the above two commands to confirm that no entries have the old host
name in the Service ID column.
Use the hcmdssrv command to restart the services on the HTnM server host to ensure that the
deletion of service information in step 11 takes effect.
(13) Change the settings of the connection-target HTnM server on the HTnM agents host.
On the HTnM agents host connected to the HTnM server, change the settings of the
connection-target HTnM server. Use the jpcnshostname command to change the
connection-target HTnM server settings. For example, to change the host name of the
connection-target HTnM server to "hostB", specify the host name and execute the command as
shown below.
If the HTnM agents connected to the HTnM server is operating in a logical host environment,
you must use the -lhost option to specify the logical host name of the HTnM agents host.
jpcnshostname -s hostB
or
jpcnshostname -s hostB -lhost < the logical host name of HTnM agents >
Start the HTnM agents programs and services on the HTnM agents host connected to the
HTnM server. Use the jpcstart command to start the services.
If the HTnM agents connected to the HTnM server is operating in a logical host environment,
use the cluster software to start the HTnM agents services.
Respecify the settings of the health check agent whose service ID includes the new host name
(the health check agent settings that you canceled in step 9).
Respecify the settings of the HTnM agent whose service ID includes the new host name (the
HTnM agent settings that you deleted in step 10).
445
If the Action Handler on the HTnM server host is specified as the Action Handler that executes
actions, you must use either Performance Monitor or the jpcalarm command on the HTnM
server host to update the alarm settings.
Edit the alarm and set PH1< the changed host name of the HTnM server host > as the Action
Handler that executes the action.
After changing the settings, check the items below in Main Console and Performance Reporter.
- Performance data collection
Make sure that performance data can be collected without any problems by operating an
HTnM agent for a period that is at least twice as long as the specified performance data
collection interval.
- jpcrpt command execution
Make sure that the collected performance data can be output without any problems.
- Report definitions and alarm definitions
Make sure that there are no problems with the report definitions and alarm definitions created.
- Action execution
Make sure that the action execution for the created alarms can be performed without any
problems.
- Polling
Perform polling to confirm that the polling terminates normally.
(19) Change the startup URL by referring to the section Changing the startup URL for a Tuning
15-b.2 Action to be taken if the name of an HTnM agent host was changed
(1) Delete the HTnM agents settings.
Use Performance Reporter to remove the alarm table mapping for the HTnM agent whose
service ID includes the old host name.
Stop all HTnM agents programs and services on the HTnM agents host. Use the jpcstop
command to Stop the services.
446
If the KAVE05217-E message is output and the services fail to Stop when the jpcstop command
is executed, edit the jpchosts file so that the old host name can be resolved, and then execute the
command again. Delete these settings after the services are Stopped.
Follow the procedure below to check the currently configured physical host name on the HTnM
agents host.
a)
Use the following command to check the monitoring host name acquisition method
jpcconf host hostmode -display
b)
Based on the monitoring host name acquisition method confirmed in a) above, use the
appropriate command below to check the physical host name of the OS.
1.
2.
(4) Change the monitoring host name of the HTnM agents host.
On the HTnM agents host, execute the jpcconf host hostname command to change the
monitoring host name. The command examples shown below change the physical host name to
"hostB".
1.
In Windows:
jpcconf host hostname -newhost hostB -d d:\backup -dbconvert convert
2.
In UNIX:
jpcconf host hostname -newhost hostB -d /var/tmp/backup -dbconvert convert
(5) Change the jpchosts file, hosts file, and DNS settings as necessary, so that the name of the
(7) Delete the service information from the HTnM server host.
If service information that includes the old host name remains, delete the service information by
using the following procedure:
If the HTnM server is operating in a logical host environment, you must use the lhost option to
specify the logical host name of the HTnM server host.
1.
Execute the jpcctrl list command to search for the remaining service information.
447
2.
If the jpcctrl list "*" command results include service information with service IDs that
include the old host name in the Service ID column and with the changed host name in
Host Name, specify the host names and execute the command as follows:
jpcctrl delete "???< the old host name >" host=< the changed host name >
jpcctrl delete "*[< the old host name >]" host=< the changed host name >
or
jpcctrl delete "???< the old host name >" host=< the changed host name >
lhost=< the logical host name of the HTnM server host >
jpcctrl delete "*[< the old host name >]" host=< the changed host name > lhost=< the
logical host name of the HTnM server host >
If the KAVE05233-W message is output and the service information fails to delete when
the command is executed, specify the force option and execute the command again.
448
jpcctrl delete "???< the old host name >" host=< the changed host name > -force
jpcctrl delete "*[< the old host name >]" host=< the changed host name > -force
or
jpcctrl delete "???< the old host name >" host=< the changed host name > lhost=< the
logical host name of the HTnM server host > -force
jpcctrl delete "*[< the old host name >]" host=< the changed host name > lhost=< the
logical host name of the HTnM server host > -force
3.
Execute the jpcctrl list command to confirm that the service information was correctly
deleted.
jpcctrl list "*" host=< the old host name >
jpcctrl list "*" host=< the changed host name >
or
jpcctrl list "*" host=< the old host name > lhost=< the logical host name of the HTnM
server host >
jpcctrl list "*" host=< the changed host name > lhost=< the logical host name of the HTnM
server host >
Check the output of the above two commands to confirm that no entries have the old host
name in the Service ID column.
Use the hcmdssrv command to restart the services on the HTnM server host to ensure that the
deletion of service information in step 7 takes effect.
If the HTnM server is operating in a logical host environment, use the cluster software to start
the HTnM server services.
Start the HTnM agents programs and services. Use the jpcstart command to start the services.
Respecify the settings of the HTnM agent whose service ID includes the new host name (the
HTnM agent settings that you deleted in step 1).
If the Action Handler on the HTnM server host is specified as the Action Handler that executes
actions, you must use either Performance Monitor or the jpcalarm command on the HTnM
server host to update the alarm settings.
Edit the alarm and set PH1< the changed host name of the HTnM server host > as the Action
Handler that executes the action.
449
After changing the settings, check the items below in Main Console and Performance Reporter.
- Performance data collection
Make sure that performance data can be collected without any problems by operating a HTnM
agents for a period that is at least twice as long as the specified performance data collection
interval.
- jpcrpt command execution
Make sure that the collected performance data can be output without any problems.
- Report definitions and alarm definitions
Make sure that there are no problems with the report definitions and alarm definitions created.
- Action execution
Make sure that the action execution for the created alarms can be performed without any
problems.
- Polling
Perform polling to confirm that the polling terminates normally.
450
15-c Using RAS information to check whether the host name was changed in the correct
manner
Note: The files used in the following flowchart are included in the RAS information for Collection
Manager or for the agent.
In the jpccomm.ini file, under [Common Section], check the values of
the Get Host Mode entry (a) and the Host Name entry (b) .
0 or 1
In the hostname.txt file, check the
physical host name (c) (*1).
Yes
No
Incorrectly changed
Correctly changed
Figure 15-c.1-1 How to use RAS information to check whether the host name was changed in the
correct manner
(*1) The procedure for checking the physical host name differs depending on the OS type and the value
of the Get Host Mode entry, as shown below.
#
OS type
Windows
Value of
Get Host Mode
0 or 1
UNIX
Procedure
Check the contents of the hostname.txt file, which contains only
host names.
In the hostname.txt file, in the output of the uname command,
check the name of the host.
In the hostname.txt file, in the output of the hostname
command, check the name of the host.
451
452
Note:
- If you perform this procedure, all Hybrid Store data will be deleted.
- This procedure cannot be performed in cluster environments.
- If RAID Agent and NAS Agent are on the same host, you cannot change the data storage
format from Hybrid Store to Store database independently for RAID Agent.
The configuration and procedure for changing the data storage format are shown below.
RAID Agent
NAS Agent
Hybrid Store
Hybrid Store
Agent whose
data storage
format is to be
changed
RAID Agent
Possibility
of change
Procedure for
change
P: Possible
I:Impossible
RAID Agent
NAS Agent
StoreDB
StoreDB
Procedure A
NAS Agent
2
Hybrid Store
Hybrid Store
RAID Agent
StoreDB
Hybrid Store
Hybrid Store
Hybrid Store
NAS Agent
Hybrid Store
StoreDB
Procedure B
Hybrid Store
Store DB
RAID Agent
StoreDB
StoreDB
Procedure A
Hybrid Store
RAID Agent
StoreDB
Procedure A
Store DB
Hybrid Store
NAS Agent
StoreDB
StoreDB
Procedure A
Hybrid Store
NAS Agent
StoreDB
Procedure C
Following is the Each procedure for changing the data storage format.
Procedure A:
(1) Execute the following htmsrv command on Agent host to stop all services:
453
<installation-folder>\htnm\agent\system\data_file_manage.ini
For UNIX:
/opt/jp1pc/htnm/agent/system/data_file_manage.ini
- Modification
<Before modification>
[Mode]
Database Type=ScalableDB
<After modification>
[Mode]
Database Type=Store
- Modification
<Before modification>
add.jvm.arg=-Xmx6144m
<After modification>
add.jvm.arg=-Xmx1024m
If the migration_status.ini file exists, delete it. Repeat this step for each type of
Agent.
- Location where the files are stored
For Windows:
<installation-folder>\agtX\ migration_status.ini
For UNIX:
/opt/jp1pc/agtX/migration_status.ini
support_switch_db.ini.tmpl.
If the support_switch_db.ini file exists, rename it to
support_switch_db.ini.tmpl. Repeat this step for each type of Agent.
454
For Windows:
<installation-folder>\agtX\support_switch_db.ini
For UNIX:
/opt/jp1pc/agtX/support_switch_db.ini
If the dbmigrating.dat file exists, delete it. Repeat this step for each type of Agent.
- Location where the files are stored
For Windows:
<installation-folder>\agtX\agent\dbmigrating.dat
For UNIX:
/opt/jp1pc/agtX/agent/dbmigrating.dat
If
you
changed
the
default
storage
location
of
the
data,
see
the
(8) Specify the output destination of the operating performance information file for RAID Agent.
Follow this step if you are using Tuning Manager API on RAID Agent, and you want to
change the output destination of the operating performance information file. If you want to
Change the output destination, see the Hitachi Command Suite Tuning Manager Agent
Administration Guide.
(9) Execute the following htmsrv command to start all services:
Procedure B:
If RAID Agent and NAS Agent both use Hybrid Store, and you want to change the data storage
format to Store DB independently for NAS Agent, follow the steps below:
(1) Execute the following htmsrv command on Agent host to stop all services:
If the migration_status.ini file exists, delete it. Repeat this step for each type of
Agent.
455
support_switch_db.ini.tmpl.
If the support_switch_db.ini file exists, rename it to
support_switch_db.ini.tmpl. Repeat this step for each type of Agent.
If the dbmigrating.dat file exists, delete it. Repeat this step for each type of Agent.
- Location where the files are stored
For Windows:
<installation-folder>\agtX\agent\dbmigrating.dat
For UNIX:
/opt/jp1pc/agtX/agent/dbmigrating.dat
If
you
changed
the
default
storage
location
of
the
data,
see
the
Procedure C:
If only NAS Agent is installed, follow the steps below:
(1) Execute the following htmsrv command on Agent host to stop all services:
- Modification
<Before modification>
[Mode]
Database Type=ScalableDB
<After modification>
[Mode]
Database Type=Store
If the migration_status.ini file exists, delete it. Repeat this step for each type of
Agent.
- Location where the files are stored
For Windows:
<installation-folder>\agtX\ migration_status.ini
For UNIX:
/opt/jp1pc/agtX/migration_status.ini
support_switch_db.ini.tmpl.
If the support_switch_db.ini file exists, rename it to
support_switch_db.ini.tmpl. Repeat this step for each type of Agent.
If the dbmigrating.dat file exists, delete it. Repeat this step for each type of Agent.
- Location where the files are stored
457
For Windows:
<installation-folder>\agtX\agent\dbmigrating.dat
For UNIX:
/opt/jp1pc/agtX/agent/dbmigrating.dat
If
you
changed
the
default
storage
location
of
the
data,
see
the
htmrestctrl off
(8) Execute the following jpcstart command to start all services:
jpcstart all
458
19-a How to check the data storage format of Agent (Version 8.1.3 to earlier than 8.2.1)
RAID Agent version 8.1.3 and later can use two data storage formats, the Store database and the
Hybrid Store. To check the data storage format of the Agent, see the following two files included
in the RAS materials, and see table 19-1 to determine the format:
- data_file_manage.ini
- support_switch_db.ini
Table 19-1 How to determine the data storage format (Version 8.1.3 to earlier than 8.2.1)
#
data_file_manage.ini
support_switch_db.ini
data_file_manage.ini
ScalableDB
Hybrid Store
ScalableDB
Store database
Store
Store database
Store
Store database
(Empty string)
Store database#1
(Empty string)
Store database
Store database
Store database
#1: Currently migrating to Hybrid Store, or was terminated abnormally during the migration.
459
19-b How to check the data storage format of Agent (Version 8.2.1 or later)
RAID Agent and NAS Agent version 8.2.1 and later can use two data storage formats, the Store
data base and the Hybrid Store. To check the data storage format used in the Agent, see the
following files included in the RAS materials, and see table 19-2 to determine the format used for
each Agent type:
- data_file_manage.ini (Only one copy of this file exists in the RAS materials.)
- support_switch_db.ini (This file exists for each type of Agent.)
- dbmigrating.dat (This file exists for each type of Agent.)
Table 19-2 How to determine the data storage format (Version 8.2.1 or later)
#
data_file_ma
support_switc
nage.ini
data_file_manage.ini
h_db.ini
dbmigrating.dat
ScalableDB
Store database#1
ScalableDB
Hybrid Store
ScalableDB
Store database#1
ScalableDB
Store database
Store
Store database#1
Store
Store database
Store
Store database#1
Store
Store database
(Empty string)
Store database#1
10
(Empty string)
Hybrid Store
11
(Empty string)
Store database#1
12
(Empty string)
Store database
13
Store database#1
14
Store database
15
Store database
16
Store database
#1: Currently migrating to Hybrid Store, or was terminated abnormally during the migration.
460
-End of document-
461