Hitachi Tuning Manager: Troubleshooting Guide 08-40-00 Rev01 2016/2/1

FE-94HC095-41
Hitachi Tuning Manager

Troubleshooting Guide
08-40-00 Rev01
2016/2/1
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.
1 Hitachi Proprietary Information

-Preface-
This 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).
(b) Using a script to execute a command provided by the product

As a result of the changes to the paths and command names, you might need to modify the
name and path of the command you want to execute.
(c) Substituting terms when using this document

For details about the changes made to the specifications for version 8, such as the installation
paths, command names, and port numbers, see the following manual. When reading the

manual, substitute the terms used in this document with those used in the manual.
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 Contents revised Date of revision Revised by
th
1 HiCommand Tuning Manager Troubleshooting Guide (for R5.0) 6 /March/2006 Fukuda
th
2 HiCommand Tuning Manager Troubleshooting Guide (for R5.5) 29 /March/2007 Muraoka
3 HiCommand Tuning Manager Troubleshooting Guide (for R5.7) 4th/June/2007 Fukuda
st
4 HiCommand Tuning Manager Troubleshooting Guide (for R5.8) 31 /August/2007 Fukuda
th
5 HiCommand Tuning Manager Troubleshooting Guide (for R5.8 Revised) 14 /September/2007 Fukuda
6 HiCommand Tuning Manager Troubleshooting Guide (for R5.9) 27th/December/2007 Fukuda
th
7 Hitachi Tuning Manager Troubleshooting Guide (for R6.0) 30 /June/2008 Nishimoto
8 Hitachi Tuning Manager Troubleshooting Guide (for R6.0 1st Revised) 15th/July/2008 Nishimoto
th
9 Hitachi Tuning Manager Troubleshooting Guide (06-00-01 Rev02) 6 /August/2008 Nishimoto
st
10 Hitachi Tuning Manager Troubleshooting Guide (06-10-00 Rev01) 31 /October/2008 Nishimoto
11 Hitachi Tuning Manager Troubleshooting Guide (06-10-00 Rev02) 28th/November/2008 Nishimoto
th
12 Hitachi Tuning Manager Troubleshooting Guide (06-20-00 Rev01) 28 /May/2009 Nishimoto
th
13 Hitachi Tuning Manager Troubleshooting Guide (06-30-00 Rev01) 30 /November/2009 Fukuda
14 Hitachi Tuning Manager Troubleshooting Guide (06-30-00 Rev02) 28th/December/2009 Hisatomi
th
15 Hitachi Tuning Manager Troubleshooting Guide (06-30-00 Rev03) 5 /March/2010 Tanaka
16 Hitachi Tuning Manager Troubleshooting Guide (06-40-00 Rev01) 28th/April/2010 Tanaka
th
17 Hitachi Tuning Manager Troubleshooting Guide (06-40-00 Rev02) 30 /June/2010 Tanaka
th
18 Hitachi Tuning Manager Troubleshooting Guide (07-00-00 Rev01) 17 / September /2010 Tanaka
19 Hitachi Tuning Manager Troubleshooting Guide (07-00-00 Rev02) 30th/ September /2010 Tanaka
th
20 Hitachi Tuning Manager Troubleshooting Guide (07-10-00 Rev01) 15 /April/2011 Fujimaki
st
21 Hitachi Tuning Manager Troubleshooting Guide (07-11-00 Rev01) 31 /July/2011 Fujimaki
22 Hitachi Tuning Manager Troubleshooting Guide (07-20-00 Rev01) 31st/October/2011 Y.Yamada
st
23 Hitachi Tuning Manager Troubleshooting Guide (07-21-00 Rev01) 21 /February/2012 Y.Yamada
24 Hitachi Tuning Manager Troubleshooting Guide (07-30-00 Rev01) 31st/May/2012 Y.Yamada
st
25 Hitachi Tuning Manager Troubleshooting Guide (07-31-00 Rev01) 31 /July/2012 F.Kobayashi
st
26 Hitachi Tuning Manager Troubleshooting Guide (07-40-00 Rev01) 31 /October/2012 F.Kobayashi
27 Hitachi Tuning Manager Troubleshooting Guide (07-41-00 Rev01) 4th/February/2013 Y.Yamada
th
28 Hitachi Tuning Manager Troubleshooting Guide (07-50-00 Rev01) 29 /April/2013 F.Kobayashi
th
29 Hitachi Tuning Manager Troubleshooting Guide (07-60-00 Rev01) 30 /September/2013 F.Kobayashi

30 Hitachi Tuning Manager Troubleshooting Guide (07-61-00 Rev01) 30th/December/2013 F.Kobayashi
st
31 Hitachi Tuning Manager Troubleshooting Guide (08-00-00 Rev01) 31 /March/2014 F.Kobayashi
th
33 Hitachi Tuning Manager Troubleshooting Guide (08-01-00 Rev01) 28th/July/2014 Y.Yamada
th
34 Hitachi Tuning Manager Troubleshooting Guide (08-10-00 Rev01) 6 /October/2014 F.Kobayashi
35 Hitachi Tuning Manager Troubleshooting Guide (08-11-00 Rev01) 1st/December/2014 F.Kobayashi
st
36 Hitachi Tuning Manager Troubleshooting Guide (08-12-00 Rev01) 2 /February/2015 Y.Yamada
st
37 Hitachi Tuning Manager Troubleshooting Guide (08-13-00 Rev01) 2 /March/2015 Y.Yamada
38 Hitachi Tuning Manager Troubleshooting Guide (08-13-00 Rev02) 9th/April/2015 F.Kobayashi
th
th
40 Hitachi Tuning Manager Troubleshooting Guide (08-20-00 Rev01) 29 /June/2015 F.Kobayashi
41 Hitachi Tuning Manager Troubleshooting Guide (08-20-01 Rev01) 3rd/August/2015 F.Kobayashi
nd
42 Hitachi Tuning Manager Troubleshooting Guide (08-21-00 Rev01) 2 /November/2015 F.Kobayashi
43 Hitachi Tuning Manager Troubleshooting Guide (08-21-00 Rev02) 16th/November/2015 F.Kobayashi
th
44 Hitachi Tuning Manager Troubleshooting Guide (08-40-00 Rev01) 1 /February/2016 F.Kobayashi

-Abbreviations of Hitachi products-
This manual uses the following abbreviations for Hitachi product names.
Abbreviation Full name of meaning
Agent A generic name for:
Hitachi Tuning Manager Agent for Network Attached Storage
Hitachi Tuning Manager Agent for Oracle
Hitachi Tuning Manager Agent for Platform (for UNIX systems)
Hitachi Tuning Manager Agent for Platform (for Windows systems)
Hitachi Tuning Manager Agent for RAID
Hitachi Tuning Manager Agent for RAID Map
Hitachi Tuning Manager Agent for Microsoft SQL Server
Hitachi Tuning Manager Agent for Microsoft Exchange Server
Hitachi Tuning Manager Agent for SAN Switch
Hitachi Tuning Manager Agent for IBM DB2 (*1)
Hitachi Tuning Manager Agent for HealthCheck
Hitachi Tuning Manager Agent for Enterprise Applications (Supported
in Ver.7.1.1 or later)
(*1) This name is used in Ver.7.4.1 or later. In Ver.6 to 7.4, the following
name is used:
Hitachi Tuning Manager - Agent for IBM DB2 Universal Database
Collection Manager Hitachi Tuning Manager 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 Hitachi Tuning Manager Agent for Microsoft Exchange Server
Agent for Server System Hitachi Tuning Manager Agent for Server System
Main Console Hitachi Tuning Manager Main Console
NAS Agent Hitachi Tuning Manager Agent for Network Attached Storage
Oracle Agent Hitachi Tuning Manager Agent for Oracle
Platform Agent(Unix) Hitachi Tuning Manager Agent for Platform (for UNIX systems)
Platform Agent(Windows) Hitachi Tuning Manager Agent for Platform (for Windows systems)
Performance Reporter Hitachi Tuning Manager Performance Reporter
or PR
RAID Agent Hitachi Tuning Manager Agent for RAID
RAID Map Agent Hitachi Tuning Manager Agent for RAID Map
SQL Agent Hitachi Tuning Manager Agent for Microsoft SQL Server

Switch Agent Hitachi Tuning Manager Agent for SAN Switch
EAP Agent Hitachi Tuning Manager Agent for Enterprise Applications
Tuning Manager server A generic name for:
# Hitachi Tuning Manager Collection Manager
# Hitachi Tuning Manager Main Console
# Hitachi Tuning Manager Performance Reporter
# Hitachi Tuning Manager Tuning Service (In Ver.6.0 to earlier than 8.0)
HealthCheck Agent Hitachi Tuning Manager Agent for HealthCheck
OCI Oracle Call Interface
ADO ActiveX Data Object
Tuning Manager REST HCS Tuning Manager REST Application Service
Application Service
or HTnM REST Application
Service
HTnMAgent REST Tuning Manager - Agent REST Application Service
Application Service
HTnM-Agent REST Tuning Manager - Agent REST Web Service
Web Service
HTnM-Agent REST Services A generic name for:
Tuning Manager - Agent REST Application Service
Tuning Manager - Agent REST Web Service

-Abbreviation of other products or terms-
This manual uses the following abbreviations for other product names or terms.
Abbreviation Full name of meaning
API Application Program Interface
CLI Command Line Interface
CLPR Cache Logical PaRtition
CRC Cyclic Redundancy Check
DAMP2 Disc Array Management Program 2
DHCP Dynamic Host Configuration Protocol
DLL Dynamic Linking Library
DNS Domain Name System
EFCM Enterprise Fabric Connectivity Manager
FQDN Fully Qualified Domain Name
GBIC Gigabit Interface Converter
HA High Availability
HBA Host Bus Adapter
HDT Hitachi Dynamic Tiering
HDU Hard Disk Unit
HTnM Hitachi Tuning Manager
HTM Hitachi Tuning Manager
HTML Hyper Text Markup Language
I/O Input/Output
IP Internet Protocol
Ipv4 Internet Protocol Version 4
Ipv6 Internet Protocol Version 6
GUI Graphical User Interface
GUID Globally Unique Identifier
JRE Java2 Runtime Environment
LAN Local Area Network
LDEV Logical Device
LUSE Logical Unit Size Expansion
LUN Logical Unit Number
MIB Management Information Base
NAS Network Attached Storage
NIC Network Interface Card
OS Operating System
RAID Redundant Arrays of Inexpensive Disks
RAID Manager LIB Raid Manager Library

RFC Remote Function Call
SAN Storage Area Network
SCM Service Control Manager
SNMP Simple Network Management Protocol
SLPR Storage Logical PaRtition
SSL Secure Socket Layer
SSO Single Sign On
SVP Service Processor
SP Service Pack
TBD To Be Determined
TCP Transmission Control Protocol
TIA Trouble Information Acquisition
UDP User Datagram Protocol
VLAN Virtual Local Area Network
VxVM VERITAS Volume Manager
WWN World Wide Name
WWW World Wide Web
XML Extensible Markup Language
NTFS NT File System
-Explanation of Terms for Version 8 or Later-

This manual for version 8 or later uses the following terms:
Term Meaning
HBase Refers to both the 32-bit version and 64-bit version of HBase
HBase32 Refers specifically to the 32-bit version of HBase
HBase64 Refers specifically to the 64-bit version of HBase
Notations: Installation Directories

This manual uses the following notations for installation directories:
Notation Description Examples (*1)
<HBase-Installation-dir The installation directory for For Windows:
ectory> both the 32-bit version and C:\Program Files (x86)\HiCommand\Base
the 64-bit version of Hitachi or
Command Suite Common C:\Program Files\HiCommand\Base64
Component
For Unix:
/opt/HiCommand/Base

or
/opt/HiCommand/Base64
<HBase32-Installation- The installation directory for For Windows:
directory> the 32-bit version of Hitachi C:\Program Files (x86)\HiCommand\Base
Command Suite Common
Component For Unix:
/opt/HiCommand/Base
<HBase64-Installation- The installation directory for For Windows:
directory> the 64-bit version of Hitachi C:\Program Files\HiCommand\Base64
Command Suite Common
Component For Unix:
<HTnM-Installation-dir The installation directory for For Windows:
ectory> Hitachi Tuning Manager C:\Program Files (x86)\HiCommand\TuningManager
or
C:\Program Files\HiCommand\TuningManager
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 Later-

The 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 Corresponding term for version 8 or later
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

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432N HKEY_LOCAL_MACHINE\SOFTWARE
ode
HiRDBClusterService_HD0 HiRDBClusterService_HD1
HiRDBEmbeddedEdition_HD0 HiRDBEmbeddedEdition_HD1

Contents
1. Related Publications ................................................................................................................................. 20
2. Error Handling Procedures...................................................................................................................... 22

2.1 General flowchart ............................................................................................................ 22
2.2. Installation error ............................................................................................................. 23
2.2.1. Error during installation of Tuning Manager server(Ver.5 or earlier) ........................... 23
2.2.2. Error during installation of Tuning Manager server(Ver.6.0.0 to 7.4.0) ........................ 23
2.2.3. Error during installation of Tuning Manager server(Ver.7.4.1 or later)......................... 25
2.2.4. Error during installation of Agent ............................................................................. 34
2.3. Error during startup of a service .................................................................................... 37
2.3.1. Error during startup of a Tuning Manager server service(Ver.5 or earlier) .............. 37
2.3.2. Error during startup of a Tuning Manager server service(Ver.6 or later) ................. 37
2.3.3. Error during startup of an Agent service .............................................................. 38
2.3.4. Error during startup of Tuning Manager REST service (Ver. 8 or later) .................. 59
2.4. Tuning Manager server error failing to update data ...................................................... 61
2.4.1. Error analysis using Main Console(Ver.5 or earlier) ............................................. 63
2.4.2. Error analysis using Main Console(Ver.6 or later) ................................................ 64
2.4.3. Error analysis using the jpcctrl list command ....................................................... 67
2.4.4. Error analysis using PR reports........................................................................... 68
2.4.5. Other considerations .......................................................................................... 70
2.5. Errors in Tuning Manager API ....................................................................................... 73
2.6. Errors when using the alert function .............................................................................. 74
3. Information for Troubleshooting ............................................................................................................. 75
4. RAS Collection .......................................................................................................................................... 77

4.1. RAS information collection commands ........................................................................... 77
4.1.1. hcmdsgetlogs command ..................................................................................... 78
4.1.2. htm-getlogs command ....................................................................................... 92
4.1.3. htm-dump command .......................................................................................... 93
4.1.4. jpcprras command ............................................................................................. 94
4.1.5. jpcras command ................................................................................................ 95
4.2. RAS information manually collected .............................................................................. 96
4.2.1 Installation log files(Ver.5 or earlier) ......................................................................... 97
4.2.2 Installation log files(Ver.6 or later) ............................................................................ 97
4.2.3 Switch Agent ......................................................................................................... 100
4.2.4 EAP Agent ............................................................................................................ 104
4.2.5 htm-csv-convert..................................................................................................... 104
4.3. The required time for executing the RAS command ..................................................... 104
4.4 Properties of internal logs ..................................................................................................... 105
4.4.1 The number and size of Main Console trace log files ................................................ 105
4.4.2 Number, size, and output level of Hybrid Store trace log files ................................... 107
4.5 The problems in acquiring RAS information and the contingency plan. (Only in
Ver.6.4) 108
4.5.1 The background ................................................................................................ 108
4.5.2 Overview of the contingency plan .............................................................. 109
4.5.3 Prerequisites ....................................................................................................110
4.5.4 Details of the contingency plan ...................................................................110
4.6. Collecting data when a problem occurs while displaying a chart in Adobe Flash
Player (Tuning Manager server v7.3.0 and later) ....................................................................... 114
5. Architecture ............................................................................................................................................. 117

5.1 Process composition ....................................................................................................... 117
5.2 Communication Sequence ............................................................................................. 125
5.2.1 Sequence for starting up the service of Collection Manager/Agents ..................... 125
5.2.1 Sequence for starting up the service of Tuning Manager server ........................... 129
6. How to Start or Stop Services................................................................................................................. 131

6.1. Tuning Manager server services ................................................................................... 131
6.2. Unused numbers ........................................................................................................... 131
6.3. HiRDB services.............................................................................................................. 131
6.4. Agent services ................................................................................................................ 131
7. Other Information .................................................................................................................................. 133

7.1. Disabling IPv6 (Ver. 6 or later)...................................................................................... 133
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) ............................................................................................................... 134
7.3. Notice for linkage with Tiered Storage Manager .......................................................... 134
7.4. Notes on the hcmdsdbclustersetup command ............................................................... 136
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 ......................................................................................... 137
7.6. Using the jpcctrl delete command with the force option (this option is in
non-public to user), to forcibly delete node information ............................................................. 138
7.7 Store database error detection tool (HTnM 6.4 or later) ...................................................... 142
7.7.1 Overview of the Store database error detection tool .................................................. 142
7.7.2 How to use the Store database error detection tool.................................................... 146
7.7.3 If an error is found in a Store database ..................................................................... 156
7.7.4 Tool performance................................................................................................... 157
7.7.5 Troubleshooting..................................................................................................... 158
7.7.6 Detailed specifications ........................................................................................... 159

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-b.1 Purpose .......................................................................................................... 206
3-b.2 Applicable Versions ......................................................................................... 206
3-b.3 Overview of deleting Tuning Manager server .................................................... 206
3-b.4 Deleting Tuning Manager server without deleting Agent .................................... 209
3-b.5 Forcibly Deleting Tuning Manager server ..........................................................211
3-c 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 Purpose .......................................................................................................... 239
3-d.2 Applicable Versions ......................................................................................... 239
3-d.3 Overview of deleting Tuning Manager server .................................................... 239
3-d.4 Deleting Tuning Manager server without deleting Agent .................................... 241

3-d.5 Forcibly Deleting Tuning Manager server ......................................................... 242
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 Purpose .......................................................................................................... 250
3-e.2 Support version ............................................................................................... 250
3-e.3 Notes for the operation .................................................................................... 250
3-e.4 The flow of the force deletion and re-install the agent ........................................ 251
3-e.5 Uninstall by the uninstaller............................................................................... 252
3-e.6 Force deletion of the agent ............................................................................... 252
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 Purpose .......................................................................................................... 261
3-f.2 Support version ............................................................................................... 261
3-f.3 Notes for the operation .................................................................................... 262
3-f.4 The flow of the force deletion and re-install the agent ........................................ 262
3-f.5 Uninstall by the uninstaller............................................................................... 263
3-f.6 Force deletion of the agent ............................................................................... 263
3-g Deleting Tuning Manager server for Linux (In Ver.7.1.0 to earlier than 8.0.0) ........... 265
3-g.1 Purpose .......................................................................................................... 265
3-g.2 Applicable Versions ......................................................................................... 265
3-g.3 Overview of deleting Tuning Manager server .................................................... 265
3-g.4 Deleting Tuning Manager server without deleting Agent .................................... 267
3-g.5 Forcibly Deleting Tuning Manager server ......................................................... 268
3-h Deleting Tuning Manager server for Windows (Ver.8 or later) ..................................... 276
3-h.1 Purpose .......................................................................................................... 276
3-h.2 Applicable Versions ......................................................................................... 276
3-h.3 Overview of deleting Tuning Manager server .................................................... 276
3-h.4 Deleting Tuning Manager server without deleting Agent .................................... 277
3-h.5 Forcibly Deleting Tuning Manager server ......................................................... 278
3-i Deleting Tuning Manager server for Linux (Ver.8 or later)................................................... 314
3-i.1 Purpose .......................................................................................................... 314
3-i.2 Applicable Versions ......................................................................................... 314
3-i.3 Overview of deleting Tuning Manager server .................................................... 314
3-i.4 Deleting Tuning Manager server without deleting Agent .................................... 316
3-i.5 Forcibly Deleting Tuning Manager server ......................................................... 317
3-j Force uninstall of the Tuning Manager agents for Windows (Ver.8 or later) ........................ 333
3-j.1 Purpose .......................................................................................................... 333
3-j.2 Support version ............................................................................................... 333
3-j.3 Notes for the operation .................................................................................... 333
3-j.4 The flow of the force deletion and re-install the agent ........................................ 334

3-j.5 Uninstall by the uninstaller............................................................................... 335
3-j.6 Force deletion of the agent ............................................................................... 335
3-k Force uninstall of the Tuning Manager agents for UNIX (Ver.8 or later) ............................ 344
3-k.1 Purpose .......................................................................................................... 344
3-k.2 Support version ............................................................................................... 344
3-k.3 Notes for the operation .................................................................................... 344
3-k.4 The flow of the force deletion and re-install the agent ........................................ 345
3-k.5 Uninstall by the uninstaller............................................................................... 345
3-k.6 Force deletion of the agent ............................................................................... 346
Appendix 4 Knowledge for HiRDB Management ........................................................................................ 350

4-a Confirmation of the state of RD area .................................................................................... 350
4-b Handling of the blocked RD area .......................................................................................... 353
4-c How to extend or reduce the database log area..................................................................... 353
4-c.1 Purpose .......................................................................................................... 353
4-c.2 Support version ............................................................................................... 354
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
Appendix 5 Data Exporting Sample Script(Ver.6 or later) ......................................................................... 369
Appendix 6 For the HPE OEM version, substitute the following terms as indicated ............................... 370
Appendix 7 Backup and Restoration (Ver. 6 or later).................................................................................. 384

7-a. Backup procedure on a host on which the Tuning Manager server and Agent are installed in
a Windows environment ................................................................................................. 384
7-a.1 Purpose .......................................................................................................... 384
7-a.2 Applicable Versions ......................................................................................... 384
7-a.3 Terms ............................................................................................................. 384
7-a.4 Overview of Tuning Manager server backup procedure ...................................... 384
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
Service (Ver. 8 or later)................................................................................................... 390
7-a.8 Back up the Store database ............................................................................... 390
7-a.9 Back up the definition information files for Agent.............................................. 391
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
7-b.1 Purpose .......................................................................................................... 394
7-b.2 Prerequisites ................................................................................................... 394
7-b.3 Applicable Versions ......................................................................................... 394
7-b.4 Terms ............................................................................................................. 394
7-b.5 Overview of Tuning Manager server restoration ................................................ 395
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) Restore the definition information files for Tuning Manager REST
Service (Ver. 8.0 or later) ........................................................................................... 399
7-b.9 Restore the Store database .......................................................................... 399
7-b.10 Restore the definition information files for Agent .................................. 400
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-b.13 Restore the Hybrid Store (Ver. 8.1.3 or later)............................................... 401
7-c. Backup procedure on a host on which the Tuning Manager server and Agent are installed in
a UNIX environment ...................................................................................................... 402
7-c.1 Purpose .......................................................................................................... 402
7-c.2 Applicable Versions ......................................................................................... 402
7-c.3 Terms ............................................................................................................. 402
7-c.4 Overview of Tuning Manager server backup procedure ...................................... 403
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 Back up the Store database ............................................................................... 408
7-c.9 Back up the definition information files for Agent.............................................. 409
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 Applicable Versions ..........................................................................................411
7-d.4 Terms ..............................................................................................................411
7-d.5 Overview of Tuning Manager server restoration ................................................ 412

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) Restore the definition information files for Tuning Manager REST
Service (Ver. 8.0 or later) ........................................................................................... 416
7-d.9 Restore the Store database .......................................................................... 416
7-d.10 Restore the definition information files for Agent .................................. 417
7-d.11 Restore the definition information files for HTnM-Agent REST Services
(Ver. 8.0 or later) ........................................................................................................ 417
7-d.12 Restore the performance data for Tuning Manager API (Ver. 8.0 or later)
418
7-d.13 Restore the Hybrid Store (Ver. 8.1.3 or later)............................................... 418
Appendix 8 For the version 7.0 or later, substitute the following terms as indicated ............................... 419
Appendix 9 The policy about the access permission of files and directories ............................................. 420
Appendix 10 Cases in which HTnM did not operate normally................................................................... 421

10-a Cases in which HTnM did not operate normally due to an incorrect file ........................... 421
10-a.1 Cases.............................................................................................................. 421
10-a.2 Causes ............................................................................................................ 421
10-a.3 Solutions ........................................................................................................ 422
10-b Cases in which HTnM did not operate correctly due to an IPv6 loopback
address(ealier than 7.4.1) ............................................................................................................ 422
10-b.1 Cases.............................................................................................................. 422
10-b.2 Causes ............................................................................................................ 422
10-b.3 Solutions ........................................................................................................ 423
10-c The device information for an instance of RAID Map Agent started from a job
management product cannot be obtained ................................................................................... 423
10-c.1 Problem .......................................................................................................... 423
10-c.2 Cause ............................................................................................................. 423
10-c.3 Isolating the problem ....................................................................................... 424
10-c.4 Solution .......................................................................................................... 424
10-d Unable to launch HiRDB during the establishment of a cluster environment .................. 424
10-d.1 Problem .......................................................................................................... 424
10-d.2 Causes ............................................................................................................ 425
10-d.3 Solutions ........................................................................................................ 425
10-e Unable to launch Agent for Platform .................................................................................. 426
10-e.1 Problem .......................................................................................................... 426
10-e.2 Causes ............................................................................................................ 426
10-e.3 How to identify the cause of errors ................................................................... 427
10-e.4 Solutions ........................................................................................................ 427

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 Causes ............................................................................................................ 433
12-a.3 Solutions ........................................................................................................ 434
12-b Actions to be taken when Main Console terminates abnormally during polling ............... 435
12-b.1 Cases.............................................................................................................. 435
12-b.2 Causes ............................................................................................................ 435
12-b.3 Solutions ........................................................................................................ 435
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 Agent for RAID .............................................................................................. 438
13-b.2 Agent for SAN Switch ..................................................................................... 439
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

19-b How to check the data storage format of Agent (Version 8.2.1 or later) ............................. 460

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

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

2. Error Handling Procedures
2.1 General flowchart
Error
Check the required environment according to the ECN.
- Are the prerequisite program products and patches installed?
Check the basic items. - Is a supported operating system running?
Please note that Platform Agent(Unix) outputs core if following
patch is not applied in AIX operating system.
- xlC.aix50.rte 6.0.0.1CC Set ++ Runtime for AIX 5.0
- xlC.rte6.0.0.0CC Set ++ Runtime
Check the resources being monitored.

Are the storage, switches, and servers active?
Did the error occur during In Ver.6.0 to earlier than 7.4.1

Yes See 2.2.2. Error during installation of Tuning
installation of Tuning Manager
server? Manager server(Ver.6 or later)
No See 2.2.3. Error during installation of Tuning
Manager server(Ver.7.4.1 or later)
Did the error occur during Yes
installation of Agent? See 2.2.4. Error during installation of Agent
No
Did the error occur during
Yes See 2.3.2. Error during startup of a Tuning
startup of a Tuning
Manager server service(Ver.6 or later)
Manager server service?
No
Did the error occur during Yes

startup of an Agent service? See 2.3.3. Error during startup of an Agent service.
No
Is data displayed No See 2.4. Tuning

Main Console
Manager
error
error
causing
failingn/a
to
correctly? displaydata
update for data.
Yes
Data that must be collected:
If you cannot determine where A set of error reports described in 3.1.1 Error report.
the error occurred, collect all We recommend you use the collection commands to collect Tuning Manager logs.
logs. - On the host running Tuning Manager server:
[In Ver.6.0 to earlier than 8.0]
hcmdsgetlogs command
[In Ver.8.0 or later]
Contact the support center
and ask for investigation.
hcmds64getlogs command
- On the host running Agent:
jpcras command
For details about how to execute log commands, see 4.1. RAS information
collection commands.
Figure 2.1-1 General flow

2.2. Installation error
2.2.1. Error during installation of Tuning Manager server(Ver.5 or earlier)
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.
2.2.2. Error during installation of Tuning Manager server(Ver.6.0.0 to 7.4.0)

#1
Installation of Tuning Manager server #1 Note for installation
Stop all the series of Hitachi Storage Command Suite
other than Tuning Manager server.
If HDvM already have been installed, but it is not the
Did an error occur during

No correct version for the Tuning Manager server, the
installer outputs a warning message. If this warning
installation of Tuning Manager message is output, you need to install the correct version
server? of HDvM after Tuning Manager server is installed.
Yes #2 About the installation logs.

END . If possible, execute the RAS information collection
command to collect the data. Please collect RAS
information (RAS information that cannot be the
collected by the command, or the RAS information that
failed to be collected by the command) by manually.
(See 4.1. RAS information collection commands.)
(See 4.2. RAS information manually collected.)
#3 Check A(User check)

Make sure that the user who installs Tuning Manager
No server is a member of the Administrators group (in
Are Checks A#3, B#4, C#5, D#6,
Windows) or a root user (in UNIX).
E#7, F#8-1, G#10 and H#11
applicable?
#4 Check B (Free disk space check)
Yes -In Windows, Solaris or Linux
Make sure that the installation directory has sufficient amount of
Satisfy the requirements in Checks A, B, disk space.
-In Solaris
C, D, E, F#8-2, G, H Make sure that /var/tmp directory and /var/adm directory have
sufficient amount of disk space.
-In Linux
Make sure that /tmp directory and /var/log directory have sufficient
Re-installation of Tuning Manager server amount of disk space
See the manual for Tuning Manager server to check the amount of
disk space required for installing Tuning Manager server.

Yes #5 Check C (Amount of memory check)
Make sure that server where Tuning Manager server is installed has
re-installation of Tuning
more than 2G bytes memory.
Manager server If you install Tuning Manager server to Solaris operating system
Collect the log. or Linux operating system, please note that you have to set kernel
No #2
Collect the installation log . parameters.
See the manual for Tuning Manager server to know how to set
kernel parameters.
#6 Check D (Folder or directory permission check)

Make sure that there is write permission for the installation folder
Go to the next page. or directory.
#7 Check E (kernel parameter check)

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

#8-1 Check F (Windows NTFS information check)
Execute the following command to confirm that creation of 8.3-format file names in
Windows NTFS is enabled:
fsutil behavior query disable8dot3
1 A value of 0 indicates that automatic creation of short file names (8.3 format) is enabled.
If, for example, Windows 2000 is used and the command cannot be executed, use the
regedit command to confirm that the NtfsDisable8dot3NameCreation attribute of the
following registry key is 0 (8.3-format file name creation is enabled):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
#8-2 In Windows NTFS, use the following procedure to

No enable creation of 8.3-format file names.
Has Tuning Manager series - Execute the following command:
#9
been already installed ? fsutil behavior set disable8dot3 0
If, for example, Windows 2000 is used and the command is
Yes not available, use the regedit command to confirm that the
NtfsDisable8dot3NameCreation attribute of the following
Check the file and folder that should be registry key is 0 (enable creation of 8.3-format file names):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
located after installation by comparing with Control\FileSystem
[List of file and folder] in the manual. For - Uninstall the Tuning Manager server.
refereed manual, see Table 1.1-1. - Reboot the server machine.
If automatic creation of 8.3-format file names is disabled,
refer to the notes regarding the installation folder and
folders to be specified in the %TEMP% environment
variable.
For more information, see the following manual:
Contact the support center - In Ver.6
and ask for investigation. Hitachi Tuning Manager Software Installation Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Installation
Guide
#9 Check for file & folder #10 Check G (network status check): Ver. 7 or later
The installation of Tuning Manager series (Tuning If a network failure occurs during network installation
Manager Server/Agent) may fail if the file or folder (where the installer is on a different machine and is
those are installed previously is not located. Check the executed over a network) under Windows, the installer may
file & folders, then contact the support center with the fail. On the installation destination machine and on the
information of check result. machine where the installer is located, use the Windows
Event View window to view the system event log to check
whether a network failure occurred during installation. If a
network failure occurred, fix the network failure.
#11 Check H (Checking the prerequisite packages)
Check to make sure that all of the prerequisite packages for the
[Network failure event ID example]
product are installed on the machine on which you plan to
install the product. For details about the prerequisite packages, Source: Tcpip, Event ID: 4202
see the following manuals:
- In Version 6.0 to earlier than 7.4.1
Product requirements
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.
Figure 2.2.2-1 Error during installation of Tuning Manager server flow

2.2.3. Error during installation of Tuning Manager server(Ver.7.4.1 or later)
#1
Installation of Tuning Manager server #1 Note for installation
Stop all the series of Hitachi Storage Command Suite
other than Tuning Manager server.
If HDvM already have been installed, but it is not the

No correct version for the Tuning Manager server, the
installer outputs a warning message. If this warning
installation of Tuning Manager message is output, you need to install the correct version
server? of HDvM after Tuning Manager server is installed.
Yes
#2 About the installation logs.
END . If possible, execute the RAS information collection
command to collect the data. Please collect RAS
No information (RAS information that cannot be the
Are Checks A#3, B#4, C#5, D#6, collected by the command, or the RAS information that
E#7, F#8, G#9 and H#10 failed to be collected by the command) by manually.
applicable? (See 4.1. RAS information collection commands.)
Yes (See 4.2. RAS information manually collected.)
Satisfy the requirements in Checks A, B, C, #3 Check A(User check)

D, E, F, G, H Make sure that the user who installs Tuning Manager
server is a member of the Administrators group (in
Windows) or a root user (in UNIX).
Perform
#4 Check B (Free disk space check)
Is No 2.2.3.1.
-In Windows, Solaris or Linux
KATN00326-W message Dealing with
zero-byte file Make sure that the installation directory has sufficient amount of
output in log file#11 disk space.
-In Solaris
Make sure that /var/tmp directory and /var/adm directory have
Yes sufficient amount of disk space.
-In Linux
Make sure that /tmp directory and /var/log directory have sufficient
Re-installation of Tuning Manager server amount of disk space
See the manual for Tuning Manager server to check the amount of
disk space required for installing Tuning Manager server.

Yes
#5 Check C (Amount of memory check)
re-installation of Tuning Check the built-in memory of the server on which Tuning Manager
Manager server is installed. For version 6 to earlier than version 8, at least 2 GB of
Collect the log. memory is required. For version 8 or later, at least 4 GB of memory
No Collect the installation log .
#2 is required.
If you install Tuning Manager server to Solaris operating system
or Linux operating system, please note that you have to set kernel
parameters.
See the manual for Tuning Manager server to know how to set
kernel parameters.
Go to the next page. #6 Check D (Folder or directory permission check)

Make sure that there is write permission for the installation folder
or directory.
END .
#7 Check E (kernel parameter check)
If you install Tuning Manager server to Solaris operating system or
1 Linux operating system, make sure that kernel parameter values
satisfy Tuning Manager server requirements.

#8 Check F (network status check): Ver. 7 or later
If a network failure occurs during network installation
1 (where the installer is on a different machine and is
executed over a network) under Windows, the installer may
fail. On the installation destination machine and on the
machine where the installer is located, use the Windows
Event View window to view the system event log to check
whether a network failure occurred during installation. If a
network failure occurred, fix the network failure.
[Network failure event ID example]

No
Has Tuning Manager series Source: Tcpip, Event ID: 4202
#12
been already installed ?
Yes #9 Check G (confirmation of host name changes) (V7.6.1 or

later)
Check the file and folder that should be If you change the host name without following the
procedure in the manual(*), the IP address of the host cannot
located after installation by comparing with be resolved from the old host name. In this situation, an
[List of file and folder] in the manual. For attempt to upgrade or overwrite-install the product will fail.
refereed manual, see Table 1.1-1. This symptom occurs if 7.6.1 or a later version of this
product is already installed.
To locate the problem, check whether message
KAVE00134-E was output to the common message log
(jpclog) and whether the message contains the old host name.
If the old host name was output, change the host name back
Contact the support center to the old name, and then change the host name by following
and ask for investigation. the procedure in the manual. If you cannot restore the old
host name, take action according to the procedure in
Appendix 15-b.
(*) see the following manual:

#10 Check H (Checking the prerequisite packages) In Ver.7.4.1 to earlier than 8.0
Check to make sure that all of the prerequisite packages for the Hitachi Command Suite Tuning Manager Software
product are installed on the machine on which you plan to Installation Guide
install the product. For details about the prerequisite packages, Changing a host name after starting operations
see the following manuals:
- In Version 7.4.1 to earlier than 8.0 In Ver.8.0 or later
Hitachi Command Suite Tuning Manager Software Installation Guide Hitachi Command Suite Tuning Manager Installation Guide
Product requirements Changing a host name after starting operations
- Version 8.0 or later
Note: #11
Even in Linux (x64), some of the prerequisite packages must Check if KATN00326-W message is output in the following
be the 32-bit versions. These prerequisite packages might also log file
have 64-bit versions under similar names. Check carefully to
make sure that the 32-bit packages are installed rather than the [Trace log name]
64-bit versions. - Install trace log:
HTM_INST_LOG_MM-DD-YYYY_HH_MM_SS.trc
[Contents]
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 >
#12 Check for file & folder

The installation of Tuning Manager series (Tuning Manager
Server/Agent) may fail if the file or folder those are
installed previously is not located. Check the file & folders,
then contact the support center with the information of
check result.
Figure 2.2.3-1 Error during installation of Tuning Manager server flow

2.2.3.1. Dealing with zero-byte file
When installing Tuning Manager Server on the server where Tuning Manager Server or Common
Component have been installed and command of Common Component whose file size is zero exists,
the installation may fail.
Tuning Manager Server installer checks if a zero-byte file exist and if it exists, the log of the
installation informs the command of Common Component is a zero-byte file by KATN00326-W.
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.
[Target file for checking]

In 7.5.0 or later version, only zero-bite files that meet all of the following conditions are checked.
* Files in the bin under the installtion directory of Common Component.
* The file name starting from hcmds or cvxp.
* The extension of the file is .exe or .bat (In Windows)
[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 >
[Name of log file]

- Install trace log:HTM_INST_LOG_MM-DD-YYYY_HH_MM_SS.trc

[Recovery actions]
Necessary procdures are shown below when the message described above is output..
Confirm the version of the installed Common Component.#1
Confirm the version of the Common Component on the integrated installation media .#2
Compare result of version check #1 and #2. #3
Stop the services related to Hitachi Command Suite.#4
Confirm the status of services related to Hitachi

Command Suite.#5
No
Is the stop of services succeeded? #5
Yes
Perform the force installation of the Common Component.#6
No
Perform the force uninstall of the Tuning
Success?#7
Manager server.#8
Yes
Install the Hitachi Command Suite Product including HTnM server.
#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
Registry Base\<Common Component version number>

Key (When x64 is applied)HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\
HiCommand Base\<Common Component version number>

Value EXCurrentVersion
-In Solaris and Linux

Confirm the version by referring to the build file shown below.
<Solaris>
/opt/HiCommand/Base/sample/conf/build
<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 Ver.8.0.0 or later]

- 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.
Registry HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\HiCommand Base 64\
Key <Common Component version number>
Value EXCurrentVersion
- 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

The following is the stored directory of Common Component on the integrated installation media.
# OS Stored directory of Common Component
1 Windows < The integrated installation media path >\HCS\HBASE
2 Solaris(SPARC) < The integrated installation media path >/HCS/SPARC/HBASE
3 Linux(RHEL) < The integrated installation media path >/HCS/REDHAT/HBASE
4 Linux(SUSE) < The integrated installation media path >/HCS/SUSE/HBASE
(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.
#4 Stop the services related to Hitachi Command Suite.

(1) Services of Hitachi Command Suite products.
Execute the following command.
- In Windows
<Install directory of Common Component>\bin\hcmdssrv /stop
- In Solaris,Linux
< Install directory of Common Component >/bin/hcmdssrv -stop

- In Windows
<Install directory of Common Component>\bin\hcmd64ssrv /stop
- In Solaris,Linux
< Install directory of Common Component >/bin/hcmds64srv -stop

(2) Services of HiRDB.
- In Windows
Stop the HiRDB/EmbeddedEdition _HD0 and HiRDB/ClusterService _HD0 services in the
Services window
- In Solaris,Linux
Refer to "3-c.5.6 Stop the service of HiRDB"

- In Windows
Stop the HiRDB/EmbeddedEdition _HD1 and HiRDB/ClusterService _HD1 services in the
Services window
- In Linux
Refer to "3-i.5.6 Forcibly Stopping the HiRDB Process"
#5 Confirm the status of services related to Hitachi Command Suite.

Execute the following command. It might take a time to stop the services.
- In Windows
<Common-Component-installation-folder>\bin\hcmdssrv /statusall
- In Solaris,Linux
<Common-Component-installation-directory>/bin/hcmdssrv -statusall

- In Windows
<Common-Component-installation-folder>\bin\hcmds64srv /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> (*1,2)
- In Solaris

install.sh -ENFORCE -c <Stored Directory of Common Component on the integrated
installation media>
- In Linux
INSTALL.sh -ENFORCE -c <Stored Directory of Common Component on the integrated (*2)

installation media> -i < Common-Component-installation-directory >
(*1) Do not specify the space between /I option and the Common-Component-installation-directory
in the command.
(*2) Specify the directory which do not include the directory "Base" as the
Common-Component-installation-directory like a below.
(Example)
In the case when performing the force installation of Common Component in Linux
/mnt/HCS/REDHAT/HBASE/INSTALL.SH -ENFORCE -c /mnt/HCS/REDHAT/HBASE

-i /opt/HiCommand
#7 Check if the result of the forced installation of Common Component in the following way.
-In Windows
Check if the exit code is zero by referring to a value of the registry below.
(When x86 is applied)HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\HiCommand Base

Registry
(When x64 is applied)HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\
Key
HiCommand Base
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

- In Windows
Check if the exit code is zero by referring to a value of the registry below.
Registry HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\HiCommand Base 64

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

2.2.4. Error during installation of Agent
Installation of Agent
Yes
installation of the Agent?
No Are Checks A#1, B#2, C#3, D#4, No

E#5-1, F#8, G#9, H#10, I#11 and J#12
applicable?
Yes Did a warning occur
during installation of the Yes
Agent?
Collect the log.
#6
Collect the installation log .
No #13 No
Is Check K Satisfy the requirements in Checks
applicable? A to D, E#5-2, F to J
No
Yes Has Tuning Manager series
#7
been already installed ?
Perform Check K#13. Yes
Check the file and folder that should be

located after installation by comparing with
END [List of file and folder] in the manual. For
refereed manual, see Table 1.1-1.
Re-installation of Agent Contact the support center

No
re-installation of the Agent?
Yes
Did a warning occur during
Yes installation of the Agent?
No
Collect the log. No
Collect the installation log#6. Is Check K#13
applicable?
Yes
Perform Check K#13.

END

#1 Check A (User check) #2 Check B (Free disk space check)
Make sure that the user who installs the Agent is a Make sure that the installation folder of directory has
member of the Administrators group (in Windows) or a sufficient amount of disk space. See the manual for the
root user (in Unix). Agent to check the amount of disk space required for
installing the Agent.
#3 Check C (Amount of memory check) #4 Check D (Folder or directory permission check)

Make sure that server where Agent is installed has Make sure that there is write permission for the
sufficient memory. installation folder or directory.
See the manual for the Agent to check the required
memory for the Agent.
#5-1 Check E (Windows NTFS information check) #5-2 In Windows NTFS, use the following procedure to
Confirm that creation of 8.3-format file names in enable creation of 8.3-format file names.
Windows NTFS is enabled. - Execute the following command:
Execute the following command: fsutil behavior set disable8dot3 0
fsutil behavior query disable8dot3 If the command is not available, use the regedit
A value of zero for disable8dot3 indicates that command to confirm that the
automatic creation of short file names (8.3 format) is NtfsDisable8dot3NameCreation attribute of the
enabled. following registry key is 0 (enable creation of
If the command cannot be executed, use the regedit 8.3-format file names):
command to confirm that the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
NtfsDisable8dot3NameCreation attribute of the Set\Control\FileSystem
following registry key is 0 (8.3-format file name - Uninstall the Agent.
creation is enabled): - Reboot the server machine.
If automatic creation of 8.3-format file names is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl disabled, refer to the notes regarding the installation
Set\Control\FileSystem folder and folders to be specified in the %TEMP%
environment variable.
For more information, see the Installation Guide.
#6 About the installation logs. #7 Check for file & folder

If possible, execute the RAS information collection The installation of Tuning Manager series (Tuning
command to collect the data. Please collect RAS Manager server/Agent) may fail if the file or folder
information (RAS information that cannot be the those are installed previously is not located. Note that
collected by the command, or the RAS information that check this item especially for Agents, because some of
failed to be collected by the command) by manually. the modules are shared.
In Windows, the messages output by an Agent during Check the file & folders, then contact the support
installation are displayed as pop-up windows. In center with the information of check result.
UNIX, these messages are sent to the standard output
or standard error output. Since these messages are not
output to log files in either environment, take
screenshots of the messages.
(See 4.1. RAS information collection commands.)
(See 4.2. RAS information manually collected.)
#8 Check F (network status check): Ver. 7 or later #9 Check G (confirmation of host name changes)
If a network failure occurs during network installation (V7.6.1 or later)
(where the installer is on a different machine and is If you change the host name without following the
executed over a network) under Windows, the installer procedure in the manual(*), the IP address of the host
may fail. On the installation destination machine and on cannot be resolved from the old host name. In this
the machine where the installer is located, use the situation, an attempt to upgrade or overwrite-install the
Windows Event View window to view the system event product will fail. This symptom occurs if 7.6.1 or a
log to check whether a network failure occurred during later version of this product is already installed.
installation. If a network failure occurred, fix the To locate the problem, check whether message
network failure. KAVE00134-E was output to the common message log
(jpclog) and whether the message contains the old host
[Network failure event ID example] name.
Source: Tcpip, Event ID: 4202 If the old host name was output, change the host name
back to the old name, and then change the host name by
following the procedure in the manual. If you cannot
restore the old host name, take action according to the
procedure in Appendix 15-b.
(*) See the following manual:

In Ver.7.4.1 to earlier than 8.0.0
Hitachi Command Suite Tuning Manager Software
Installation Guide
Changing a host name after starting operations
Hitachi Command Suite Tuning ManagerInstallation
Guide
Changing a host name after starting operations

#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.
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.
#12 Check J (Checking the prerequisite packages)

Check to make sure that all of the prerequisite packages for the product are installed on the machine on which you plan to install the
product. For details about the prerequisite packages, see the following manuals:
- In Version 6.0 to earlier than 8.0
Product requirements
- Version 8.0 or later
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.
Figure 2.2.4-1 Error during installation of Agent flow

2.3. Error during startup of a service
2.3.1. Error during startup of a Tuning Manager server service(Ver.5 or earlier)
2.3.2. Error during startup of a Tuning Manager server service(Ver.6 or later)

#1 Check A (URL specification error check)
Login page opened with a Web browser. Make sure that a correct URL has been specified.
#2 Check B (Service status check)

Make sure that the Tuning Manager server service
is running.
Did the log in page
No To know how to start service of Tuning Manager
server, please see Appendix A.1.
appear?
#3 Check C (Firewall environment check)
Yes No If you attempt to open the Main Console log in
#1 #2
Are Checks A ,B , window from a remote host belonging to a
C#3, #4and D#5 different subnet, make sure that the firewall
allows the communication. The port number of
the Tuning Manager server for displaying the log
Yes in window is following:
[In Ver.6 to earlier than 8] 23015 (by default)
[In Ver.8] 22015 (by default)
Satisfy the requirements in Checks A , B, C, D.
How to change the port number of Tuning
Manager server is described in the following
manual:
- In Ver.6
HiCommand Tuning Manager software Administration
Guide
No - In Ver.7
Did the log in page Hitachi Command Suite Tuning Manager Software
appear? Administration Guide
- In Ver.8
Yes Collect the logs#6 Hitachi Command Suite Tuning Manager
Administration Guide
#4 Note for a Java environment

Contact the support center You do not need install Java because JRE is
installed together with Tuning Manager server.
#5 Check D (log check)
Did an error message appear
No Check whether error message is output to the
htmMessage.log or jpclog. And then see manual
in the login window?
of Hitachi Tuning Manager or FAQ document
contained in Hitachi Tuning Manager Log
Yes analysis guide, do the action that corresponds to
Are Checks E#7, F#8,
No the message.
G#9 applicable?
#6 About the logs
Yes Obtain the logs for Main Console, Collection
Manager, HBase, and HiRDB. You do not need
to collect Agent logs.
Satisfy the requirements in Checks E, F, G. We recommend you use the hcmdsgetlogs
command to collect maintenance information.
For details about how to use the command, see
4.1. RAS information collection commands.
Go to the next page. #7 Check E (HTnM-related service status check)

Go to the next page. Make sure that the following services are
running:
#8 Check F (HiRDB shutdown check)

1 2 Make sure that the database has not shut down.
For details about how to confirm this, see 4-a
Confirmation of the state of RD area in Appendix
4 Knowledge for HiRDB Manager.

1 2
No
Could you log in to the
Tuning Manager server?
No
Yes Are Checks H#10
and I#11 applicable?
Yes Collect the logs#6.

END
Satisfy the requirements in Checks H, I.
#9 Check G (HDvM setup check)

- Make sure that the HDvM services are running.
- Use the htm-dvm-setup -l command to make sure that
Yes HDvM is connectable.
Could you log in to the - Make sure that the firewall permits the port number
Tuning Manager server? for HDvM.
No
END
Collect the logs#5.

#10 Check H (License key check)
At least one subsystem license key must be entered
before you can log in. Make sure that the license key
has been entered.
#11 Check I(Account information check)
Main Console uses one default log in account,
system. If you cannot log in using this account,
contact the HTnM administrator to make sure that
account information is correct.
Figure 2.3.2-1 Error during startup of a Tuning Manager server service flow
2.3.3. Error during startup of an Agent service

This subsection describes how to isolate the error if an Agent service cannot start.
The Agent services include Agent Collector and Agent Store.
2.3.3.1. Error during startup of an Agent Collector service

The following describes how to isolate the error when an Agent Collector service cannot start.
Starting and stopping of the Agent Collector service are controlled using the jpcstart command
and SCM (in Windows). If the Agent Collector service cannot start, check the items in Table
2.3.3.1-1.

Table 2.3.3.1-1: Agent Collector common check items
No. Check item Description
To use the jpcstart command to start the Agent service, you must have logged on
1 Account information
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
2 Agent Store running status
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
3 Master Store running status
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
4 Common message log (jpclog)
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.
Table 2.3.3.1-2: Startup control of the Agent Collector service

Agent (monitoring Monitoring target resource What the system does if an attempt to
target) Resource type Data collection method collect data from the monitoring target
has failed
Command and Library In-band/ During startup of the After the
Out-band service service
started
RAID Map Agent Server & OS commands, Standard Inquiry, In-band -- Continues the
storage and so on Agent
Platform Agent Server Win API, Performance Monitor -- Note 1 service.
(Windows) tool (attached to Windows), and
so on
Platform Agent Server OS commands, -- --
(Unix) system calls, and so on
RAID Agent Thunder SNM API Out-band --
(Thunder, AMS, storage
HUS100)
RAID Agent Lightning RAID Manager Library In-band --
(Lightning, USP) storage
Switch Agent Brocade switch In Ver.7.1 to 7.6.1: Out-band Fails to start the
(Brocade(DCFM (B-Model) Windows/Solaris/Linux:SMI-S Agent service. See
SMI Agent) (Ver. 7.1 and In Ver.8.0 or later: 2.3.3.1.1.
or later)) Brocade switch Windows/Linux: SMI-S
(M-Model)

Switch Agent Brocade switch In Ver.6.0: Out-band Fails to start the
(Brocade (Ver. 7.0 or (B-Model) Windows: SMI-S Agent service. See
earlier)) UNIX: Fabric Access API 2.3.3.1.2.
(Brocade API)
In Ver.6.1 to 7.0:
Windows/Solaris: SMI-S
(Brocade(SMI Agent (B-Model) Windows/Solaris/Linux: SMI-S Agent service. See
for FOS) (Ver. 7.1 or In Ver.8.0 or later: 2.3.3.1.2.
later)) Windows/Linux: SMI-S
Switch Agent Brocade switch In.Ver.6.0 to 6.1: Out-band Fails to start the
(McDATA (Ver. 7.0 (M-Model) Windows/UNIX: SWAPI Agent service. See
or earlier)) (McDATA API) 2.3.3.1.3.
In Ver.6.2 to 7.0:
(Brocade(SMI Agent (M-Model) Windows/Solaris/Linux: SMI-S Agent service. See
for EOS) (Ver. 7.1 or In Ver.8.0 or later: 2.3.3.1.3.
later)) Windows/Linux: SMI-S
Switch Agent CISCO switch In Ver.6.0 Out-band Fails to start the
(CISCO (Ver. 7.0 or Windows: SMI-S Agent service. See
earlier)) In Ver.6.1 to 7.0: 2.3.3.1.4.
Switch Agent CISCO switch In Ver.7.1 to 7.6.1: Out-band Fails to start the
CISCO(Seed Switch) Windows/Solaris/Linux: SMI-S Agent service. See
(Ver. 7.1 or later)) In Ver.8.0 or later: 2.3.3.1.4.
Windows/Linux: SMI-S
Switch Agent CISCO switch In Ver.7.2.1 to 7.6.1: Out-band Fails to start the
CISCO(DCNM-SAN (DCNM-SAN Windows/Solaris/Linux: SMI-S Agent service. See
SMI-S Agent) (Ver. SMI-S Agent) In Ver.8.0 or later: 2.3.3.1.5.
7.2.1 or later)) Windows/Linux: SMI-S
Oracle Agent Oracle database OCI -- Fails to start the
Agent service. See
2.3.3.1.6.
SQL Agent SQL Server ADO -- Fails to start the
database Agent service. See
2.3.3.1.7.
DB2 Agent DB2 DB2 Universal Database -- Fails to start the
Management API Agent service. See
2.3.3.1.8.

NAS Agent NAS NAS commands Out-band --
Exchange Agent Exchange Win API, Performance DLL -- Fails to start the
Server Agent service. See
2.3.3.1.9.
HealthCheck Agent -- Win API,system calls -- --
EAP Agent SAP system RFC API call -- --
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.

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))
Start of the service #1 Agent common check

See Table 2.3.3.1-1.
#2 Check A (DCFM&DCFM SMI Agent check)

Did the service No Make sure that DCFM of the version and build number
fail to start? shown in the ECN are installed.
Make sure that the services for DCFM and DCFM SMI
Yes End Agent are running.
Is Agent common check#1

No
#3 Check B (DCFM SMI Agent access information
applicable? check)
For information about the access to DCFM SMI Agent,
specify the following information that was specified
Yes when the instance was created:
- IP address (IP address of the host running DCFM
Satisfy the requirements in Agent common check. SMI Agent)
- Log in ID (DCFM SMI Agent)
- Password (DCFM SMI Agent)
If access information is incorrect, use the jpcinssetup

Yes command to update instance information.
Did the service For details about how to update instance information,
fail to start? see the manual for Switch Agent.
No
No
Are Checks A#2, B#3, C#4,
and D#5 applicable? #4 Check C (DCFM SMI Agent port status check)
End The DCFM SMI Agent uses either of the following
port numbers by default:
Yes For the HTTP protocol: 5988
For the HTTPS protocol: 5989
Satisfy the requirements in Checks A to D. Use the netstat a command to make sure that these
port numbers are displayed. If port number 5988 or
5989 is not displayed, reboot the DCFM SMI Agent
service.
No Note: The port number can be set by the user.

Did the service
fail to start?
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
1 startup procedure of Switch Agent.

1
#6 About the logs

#6 Obtain the logs for Switch Agent, and DCFM.
Collect the logs . 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
Contact the support center For details about how to use the jpcras command, see
and ask for investigation. 4.1.5. jpcras command.
You must also collect the DCFM log manually.

For details about a list of DCFM logs you must collect,
see 4.2.3.Switch Agent.
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
Start of the service See Table 2.3.3.1-1.
Did the service fail No

to start?
Yes
2
No
applicable?
Yes
Satisfy the requirements in Agent common check.
Did the service Yes

fail to start?
No Go to the next page.

1 #2 Check A (Java VM being installed check)
Switch Agent version 6.0 or later for Windows, version
6.1 to ealier than 8.0 for Solaris and version 7.1 or later
for Linux uses SMI-S, and uses Java VM environment.
This environment check is done in the startup procedure
No of Switch Agent.
Are Checks A#2 applicable?
Switch Agent version 6.0 to 6.2 for Windows uses Java
VM environment that HTM-Server has.
Make sure that HTM-Server is installed on the server
Yes where Switch Agent is installed when you monitor
Brocade switch(B-Model).
Satisfy the requirements in Check A.
No #3 About the logs

Did the service Obtain the logs for Switch Agent. You do not
fail to start? need to collect information about Main Console,
HBase, Collection Manager, InterBase/HiRDB.
We recommend you use the jpcras command to
Yes collect maintenance information
For details about how to use the jpcras
command, see 4.1.5. jpcras command.
Collect the logs#3. 2
You must also collect the Proxy Switch log. For
details about the procedure, see 4.2.3.Switch
Agent.

2
#4 Confirm that information on the monitored

Is Performance Reporter Yes switches is displayed.
displaying information on
the monitored switches? #4 Start Performance Reporter to display Switch
Detail Status (real-time) reports from Switch
No End Agent instances. Make sure that all monitored
Brocade switches (B-Model) in the monitored
fabric are listed in the report.
No
Is monitoring by Switch Agent
supported for the switches for
which information is not
displayed?
End
Yes
#5 Check the OUI code of the switch for which
Yes information is not displayed.
Does the OUI code of the
switches for which information is not The fifth to tenth bytes of the switch WWN are
displayed support monitoring?#5 the switch OUI code.
If the OUI code of the Brocade switch (B-Model)
No is listed in Table 7.9-5, the switch can be
monitored.
No
Is the Switch Agent version 7.1 or later?
Yes
Upgrade Switch Agent to a version that
Perform the steps shown in Section supports the switch OUI code for which
7.9 to add the OUI code. information is not displayed.
Is Performance Reporter
No
the monitored switches? #5

End

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

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)
Start of the service
#2 Check A (DCFM/EFCM&Bridge Agent check)
Make sure that DCFM/EFCM and Bridge Agent of the
version and build number shown in the ECN are
No installed.
Did the service
fail to start? Make sure that the services for DCFM/EFCM and
Bridge Agent are running.
Yes 2 Note: Bridge Agent only supports Switch Agent
version 6.1 or earlier.
No
Is Agent common check#1 #3 Check B (DCFM/EFCM access information check)
applicable? Make sure that DCFM/EFCM-Client can log in to
DCFM/EFCM-Server. For information about the
access to DCFM/EFCM-Server, specify the following
Yes information that was specified when the instance was
created:
Satisfy the requirements in Agent common check. - IP address (IP address of the host running
DCFM/EFCM-Server)
- Log in ID (DCFM/EFCM-Server)
- Password (DCFM/EFCM-Server)
Yes Note: Make sure that the version and build number for
Did the service DCFM/EFCM-Client match those of
fail to start? DCFM/EFCM-Server.
If access information is incorrect, use the jpcinssetup

No command to update instance information.
No For details about how to update instance information,
Are Checks A#2, B#3, C#4, see the manual for Switch Agent.
D#5 and E#6 applicable?
2 Yes #4 Check C (Bridge Agent port status check)

Bridge Agent uses two port numbers, #59520 and
#59521 (fixed). Use the netstat a command to make
sure that these port numbers are displayed. If the port
Satisfy the requirements in Checks A to D.
number #59520 or #59521 is not displayed, reboot the
Bridge Agent service.
Note: The Bridge Agent port may not open during
unexpected reboot of the server.
Did the service No Note: Bridge Agent only supports Switch Agent
version 6.1 or earlier.
fail to start?
Yes #5 Check D (Checking the number of clients accessing

EFCM)
The limited number of clients can concurrently access
Go to the next page. EFCM using the SWAPI.
2 For EFCM 07.02.00 build 1 to build 8:
Maximum number of clients: 1
For EFCM 07.02.00 build 9 or later:
Maximum number of clients: 3
If HSSM and HTnM attempt to access EFCM at the
1 same time, make sure that EFCM07.02.00 build9 or
later is used.
Note: SWAPI only supports Switch Agent version 6.1

or earlier.

#6 Check E (Java VM being installed check)
Switch Agent version 6.2 or later for Windows, version
6.2 to earlier than 8.0 for Solaris and version 7.1 or later
for Linux uses SMI-S, and uses Java VM environment.
This environment check is done in the startup procedure
of Switch Agent.
1 Switch Agent version 6.2 for Windows uses Java VM

environment that HTM-Server has.
where Switch Agent is installed when you monitor
Brocade switch(M-Model).
Collect the logs#7.
#7 About the logs

Obtain the logs for Switch Agent, and DCFM/EFCM.
Contact the support center You do not need to obtain information about Main
Console, HBase, Collection Manager,
and ask for investigation. InterBase/HiRDB.
maintenance information
For details about how to use the jpcras command, see
4.1.5. jpcras command.
You must also collect the DCFM/EFCM log manually.

For details about a list of DCFM/EFCM logs you must
collect, see 4.2.3.Switch Agent.

2 #8 Confirm that information on the monitored
switches is displayed.
Start Performance Reporter to display Switch

Is Performance Reporter Yes Detail Status (real-time) reports from Switch
displaying information on Agent instances. Make sure that all monitored
the monitored switches?#8 Brocade switches (M-Model) in the monitored
fabric are listed in the report.
No End
No #9 Check the OUI code of the switch for

Is monitoring by Switch Agent which information is not displayed.
supported for the switch for which
information is not displayed? The fifth to tenth bytes of the switch WWN
are the switch OUI code.
End If the OUI code of the Brocade switch
Yes (M-Model) is listed in Table 7.9-6, the
switch can be monitored.
Yes
Does the OUI code of the
switch for which information
is not displayed support
monitoring?#9
No
No
Is the Switch Agent version 7.1 or later?
Yes
Upgrade Switch Agent to a version that
Perform the steps shown in Section supports the OUI code of the switch for
7.9 to add the OUI code. which information is not displayed.
Is Performance Reporter
No
the monitored switches? #8

End

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

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)

#2 Check A (Seed Switch access information check and
cimserver enable check)
Use the telnet command to make sure that you can log in to
the Seed Switch. For information about the access to the
Did the service fail No Seed Switch, specify the following information that was
specified when the instance was created:
to start?
- IP address (Seed Switch)
- Log in ID (Seed Switch)
Yes - Password (Seed Switch)
End If access information is incorrect, use the jpcinssetup
command to update instance information.
No For details about how to update instance information, see
Is Agent common check#1 the documentation for Switch Agent.
applicable?
And also check whether cimserver service is enabled or
not after you log in to the switch. Actually, cimserver is
Yes embedded in CISCO switch, and it need to be enable to get
the data in SMI-S IF. Otherwise, Switch Agent fails to start
Satisfy the requirements in Agent common check. the service due to communication error.
You can check its enable or disable by using show
cimserver command. If it is disable, execute the following
command.
Yes <Step1> Execute the config terminal command to
Did the service change the administrative mode.
fail to start? <Step2> Execute the cimserver enable command.
No No
No #3 Check B (Java VM being installed check)
Are Checks A#2, B#3 applicable? Switch Agent version 6.0 or later for Windows, version 6.1
End to earlier than 8.0 for Solaris and version 7.1 or later for
Linux uses SMI-S, and uses Java VM environment. This
Yes environment check is done in the startup procedure of
Switch Agent.
Satisfy the requirements in Check A, B
Switch Agent version 6.0 to 6.2 for Windows uses Java
VM environment that HTM-Server has.
where Switch Agent is installed when you monitor Cisco
Did the service No switch
fail to start?
#4 About the logs
Obtain the logs for Switch Agent.
Yes We recommend you use the hcmdsgetlogs
command to collect maintenance
information. For details about how to use
Collect the logs#4. End the command, see 4.1. RAS information
collection commands.
You must also collect the Seed Switch log.

Contact the support center And JavaVM log files. For details about the
procedure, see 4.2.3.Switch Agent.
when using CISCO instances (7.0 or earlier) or CISCO (Seed Switch) instances (7.1 or later) to monitor
Cisco switches)

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)

#2 Check A (DCNM-SAN SMI-S Agent access information
check and cimserver enable check)
Open the DCNM-SAN login window, and check whether you
can log in to DCNM-SAN by using the following login
Did the service fail No information:
- IP address (DCNM-SAN SMI-S Agent)
to start?
- Log in ID (DCNM-SAN SMI-S Agent)
- Password (DCNM-SAN SMI-S Agent)
Yes If you cannot log in, use the jpcinssetup command to update the
End instance information.
For details about updating instance information, see the Switch
No Agent documentation.
applicable?
Yes
Satisfy the requirements in Agent common check. #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
Yes check is done in the startup procedure of Switch Agent.
Did the service
fail to start?
No #4 Check C (DCNM-SAN SMI-S Agent port status

No Are Checks A#2, B#3 and No check)
C#4applicable? The DCNM-SAN SMI-S Agent uses either of the
End following port numbers by default:
For the HTTP protocol: 5988
Yes For the HTTPS protocol: 5989
Use the netstat a command to make sure that these
port numbers are displayed. If port number 5988 or
Satisfy the requirements in Check A to C 5989 is not displayed, reboot the DCNM-SAN
SMI-S Agent service.
Note: The port number can be set by the user.

Did the service No
fail to start?
#5 About the logs
Obtain the logs for Switch Agent.
Yes We recommend you use the hcmdsgetlogs
command to collect maintenance information.
For details about how to use the command, see
Collect the logs#5. End 4.1. RAS information collection commands.
You must also collect the DCNM-SAN support

information. And JavaVM log files. For details
Contact the support center about the procedure, see 4.2.3.Switch Agent.
when using CISCO(DCNM-SAN SMI-S Agent) instances (7.2.1 or later) to monitor Cisco switches)

2.3.3.1.6. Error during startup of the Oracle Agent service #2 Check A (Oracle version check)
Make sure that the Oracle product of the version shown
in the ECN is being monitored.
#3 Check B (Oracle access information check)

Make sure that the path to ORACLE_HOME that was
Did the service No specified when the instance was created is correct.
If information about ORACLE_HOME is incorrect,
fail to start? use the jpcinssetup command to recreate instance and
specify correct information.
Yes END For details about how to recreate instance, see the
manual for Oracle Agent.
Also make sure that the following conditions exist:
No - In Unix, the permission other is set for the directory
Is Agent common check#1 specified in ORACLE_HOME.
applicable? - The value set in ORACLE_SID is correct.
- The value set in net_service_name is correct when the
connection to Oracle is done via a listener.
Yes - In Windows (x64), the installation folder name
includes neither character ( nor ).
#4 Check C (Oracle access information check)

Use the sqlplus command to make sure that you can
Yes access the Oracle database.
Did the service For information about the access to the Oracle
fail to start? database, specify the following information that was
- Oracle user
No - Oracle user password
Are Checks A#2, B#3, and
No - Oracle database name (Oracle system identifier)
C#4 applicable?
If information about Oracle user or Oracle user
password is incorrect, use the jpcinssetup command to
Yes update instance information.
If information about Oracle database name (Oracle
system identifier) is incorrect, the information cannot
Satisfy the requirements in Checks A to C. be changed by update procedure. Delete the instance
information by using the jpcinsunsetup command,
create the instance environment again by using the
jpcinssetup command.
END No For details about how to update instance information or

Did the service how to delete instance/create instance, see the manual
fail to start? for Oracle Agent.
Yes
Collect the logs#5.

#5 About the logs
Obtain the logs for Oracle Agent.
END You do not need to obtain information about Main
Contact the support center Console, HBASE, Collection Manager,
InterBase/HiRDB.
and ask for investigation. We recommend you use the jpcras command to collect
maintenance information.
Figure 2.3.3.1.6-1 Error during startup of the Oracle Agent service flow

2.3.3.1.7. Error during startup of the SQL Agent service

No #2 Check A (SQL Server version check)

Did the service fail Make sure that SQL Server of the version shown in the
to start? ECN is being monitored.
Yes END #3 Check B (SQL Server access information check)

Make sure that you can access the SQL Server
No database.
Is Agent common check#1 For information about the access to the SQL Server
applicable? instance, specify the following information that was
- SQL Server user
Yes - SQL Server user password
- SQL Server instance name
- Name of the host running SQL Server
If information about SQL Server user or SQL Server
user password or Name of the host running SQL Server
is incorrect, use the jpcinssetup command to update
Yes instance information.
Did the service fail If information about SQL Server instance name is
to start? incorrect, the information cannot be changed by update
procedure. Delete the instance information by using the
jpcinsunsetup command, create the instance
No environment again by using the jpcinssetup command.
No
Are Checks A#2 and B#3 For details about how to update instance information or
applicable? how to delete instance/create instance, see the manual
for SQL Agent.
Yes
#4 About the logs

Satisfy the requirements in Checks A and B.
Obtain the logs for SQL Agent.
You do not need to obtain information about Main
Console, HBASE, Collection Manager,
END InterBase/HiRDB.
No We recommend you use the jpcras command to collect
Did the service maintenance information.
fail to start? For details about how to use the jpcras command, see
Yes
Collect the logs#4.

END
Figure 2.3.3.1.7-1 Error during startup of the SQL Agent service flow

2.3.3.1.8. Error during startup of the DB2 Agent service

No #2 Check A (DB2 version check)

Did the service fail Make sure that DB2 of the version shown in the ECN
to start? is being monitored.
Yes END #3 Check B (status of DB2 database-manager-instance

check)
No Make sure that the DB2 database-manager-instance is
Is Agent common check#1 running.
applicable?
#4 Check C (DB2 access information check)

Yes For information about the access to the DB2, specify
the following information that was specified when the
instance was created:
Satisfy the requirements in Agent common check. - DB2 node name
- DB2 database name
- DB2 user name
- DB2 user password
Yes
Did the service fail If information about DB2 node name or DB2 database
to start? name or DB2 user name or DB2 user password is
incorrect, use the jpcinssetup command to update
instance information.
No
No For details about how to update instance information,
Are Checks A#2 , B#3 see the manual for DB2 Agent.
and C#4 applicable?
#5 About the logs
Yes Obtain the logs for DB2 Agent.
You do not need to obtain information about Main
Satisfy the requirements in Checks A, B and C. Console, HBASE, Collection Manager,
InterBase/HiRDB.
END For details about how to use the jpcras command, see
No
Did the service
fail to start?
#6 About the version of DB2
Yes Check the version of monitored DB2 by following way
<Step1> Open the contents of os_inst_pp.list file
<Step2> Check the version of file-set of DB2.
Collect the logs#5 #6. Ex1) The version of DB2 is V7
Version is shown as 7.x.x.x.
db2_07_01.xxxxx 7.x.x.x xxxx xxxx
Ex2) The version of DB2 is V8
Version is shown as 8.x.x.x
db2_08_01.xxxxx 8.x.x.x xxxx xxxx
Contact the support center [Note] in above example, x stands for arbitrary
and ask for investigation. characters.
END
Figure 2.3.3.1.8-1 Error during startup of the DB2 Agent service flow

2.3.3.1.9. Error during startup of the Exchange Agent service

No #2 Check A (Exchange Server being installed check)

Did the service fail Exchange Agent can run in the server where Exchange
to start? Server itself is installed. Exchange Agent checks
registry in following ways.
(A) Window x86 OS environment
Yes END Exchange Agent supports Exchange Server 2003 in
Windows x86 environment.
No Make sure that following registry key exists and its
Is Agent common check#1 Services Version attribute is greater than (>=) 65 by
applicable? using regedit command
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Yes Exchange\Setup
(B) Windows x64 OS environment

Satisfy the requirements in Agent common check. Exchange Agent supports Exchange Server 2007,
Exchange Server 2010, and Exchange Server 2013 in a
Windows x64 environment.
Make sure that following registry instance key exists
by using regedit command.
Did the service fail Yes
to start? 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.
Yes You do not need to obtain information about Main
Console, HBASE, Collection Manager,
InterBase/HiRDB.
Satisfy the requirements in Checks A. We recommend you use the jpcras command to collect
END
No
Did the service
fail to start?
Yes
Collect the logs#3. END

Figure 2.3.3.1.9-1 Error during startup of the Exchange Agent service flow

2.3.3.2. Error during startup of an Agent Store service
The following describes how to isolate the error when an Agent Store service cannot start.
Starting and stopping of the Agent Store service are controlled using the jpcstart command and
SCM (in Windows). Agent Store is a common component provided in PFM Manager or PFM
Base. All modules used in each Agent behave the same way.
Table 2.3.3.2-1: Agent Store check items
No. Check item Description
1 Account information 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
2 Master Store running status 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.
3 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
database details about how to change the location to store the Agent Store
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
4 Common message log Check the jpclog whether error message is out put or not. And then
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.


Did the service No
fail to start?
#2 About the logs
Obtain the logs for Agent that has failed to start.
Yes You do not need to obtain information about
End Main Console, HBase, Collection Manager,
InterBase/HiRDB.
No We recommend you use the jpcras command to
Is Agent common check#1 collect maintenance information.
applicable? For details about how to use the jpcras
Yes
Yes
Did the service fail
to start?
No Collect the logs#2.
END
Contact the support center and ask
for investigation.
Figure 2.3.3.2-1 Error during startup of an Agent Store service flow

2.3.3.3. Error during connection between Collection Manager and Agent
An Agent connects to Collection Manager when starting the service.
If Collection Manager and the Agent are installed on the same host, the Agent service cannot start
unless Collection Manager is running.
On the contrary, if Collection Manager and the Agent are installed on separate hosts, even if the
Agent service fails to connect to Collection Manager, the service can start in the Stand Alone mode.
If the Agent starts in the Stand Alone mode, it attempts to connect to Collection Manager at regular
intervals.
The Agent started in the Stand Alone mode has the following disadvantages:
(1) Main Console does not display the Agent.
(2) Performance Reporter cannot display a report for the Agent.
In other words, the problem of starting an Agent in the Stand Alone mode is that data from the
Agent cannot be displayed using a GUI although the Agent collects and stores data.
The following describes how to isolate the error when the Agent starts in the Stand Alone mode.

#1 Stand Alone mode check
If the Agent service requires a long time to start,
the Agent may have started in the Stand Alone
No mode because it could not connect to Collection
Are the Agent and Collection
Manager running on separate hosts?
Manager.
Check if the following message is output to the
jpclog:
Yes KAVE00178-W An attempt to connect to
Manager failed, so the service will be started in
stand-alone mode
No When the Status Server service is active, you can
Has the Agent started in the
#1 use the jpcctrl list command to check whether
Stand Alone mode?
the Agent service is in the Stand Alone mode. If
the Agent service is in the Stand Alone mode, the
Yes End jpcctrl list command displays S Active or S Busy
in the Status column for the Agent service. For
No details about how to use the jpcctrl list
Are Checks A#2 , B#3 command, see the manual.
and C#4 applicable?
Yes #2 Check A (Checking the running status for the

Collection Manager service)
#5
Satisfy the requirements in Checks A, B and C. Collect the logs . The Agent connects to Collection Manager when
starting the service.
On the host running Collection Manager, use the
jpcctrl list command to make sure that the
Go to the next page. Collection Manager service is running.
For details about how to use the jpcctrl list
and ask for investigation. command, see the manual.

#3 Check B (Firewall environment check)
1 If a firewall is set up between the host running
the Agent and the host running the Collection
Manager, specify the firewall to permit
connection between Collection Manager and the
Agent.
No Except for the name server for Collection
Has the Agent started in
#1 Manager, the port numbers for Collection
the Stand Alone mode? Manager and Agent are dynamically allocated by
default. You need to fix the port using the
Yes jpcnsconfig command. For details about the
End command, see the manual.
#5
Collect the logs .
#4 Check C (Checking solution of Hostname/IP
Address of Collection Manager )
Communication between Collection Manager
and Agent is done by hostname. So if it fails to
communicate with Collection Manager by using
and ask for investigation. [ping hostname] command in the host where
Agent is running, please do either of following
action.
- Register the hostname of Collection Manager to
DNS server.
- Register the hostname of Collection Manager to
hosts file of the host where Agent is running.
#5 About the logs

Obtain the logs for Collection Manager and the
Agent that has failed to start. You do not need to
obtain information about Main Console, HBase,
and InterBase/HiRDB.
We recommend you use the jpcras command to
collect maintenance information. You must
execute the jpcras command separately for the
host running the Agent and for the host running
Collection Manager.
For details about how to use the jpcras
Figure 2.3.3.3-1 Error during connection between Collection Manager and Agent flow

2.3.4. Error during startup of Tuning Manager REST service (Ver. 8 or later)
Check the log
No
Is there KATR10041-I output
in the trace log?
Yes
No
Does Check A#1, Check B#2
or Check C#3 corresponds?
END
(Running normally)
Yes
Perform actions for the non-corresponding

check items and restart the services. Collect the logs#4
Contact the Support Center

Start from the beginning
(#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

Emit the API configuration information <Legend>
from API client
No
Question
Yes
Can you connect to
Tuning Manager Server? (# 1)
(#1) The symptom of connection

Check the status of HTnM failure depends on API client. For
REST Application Service(#3) example, if you are using Socket in
Java, ConnectionException is thrown.
Is the HTTP status code of

response message 200? Start from beginning (#2) Check whether the HTTP
method, URI, header in the request
message and etc. are correctly
specified and correct mistakes. For
details, see "2 Specification of the
API" in "Tuning Manager API
Reference Guide".
response message 400 series?
(#3) If the services are stopped, start

the services.
Confirm the message ID included

in the response, and then review (#4) Take action based on the
the request. (#2) message ID. Probable causes can be
for example the authentication server
is down, required license is not
registered and etc. For details, see "4
API Messages" of "Tuning Manager
Start from beginning API Reference Guide".

response message 500?
END
(Running normally)

response message 503?
1
Is the message ID of response
message KATR00101-E?
Collect the logs

Take action based on the message ID
in the response message. (#4) 1
Contact the Support Center 1
Start from beginning
Figure 2.3.4-2 Connection to Tuning Manager REST Service from client API flow

2.4. Tuning Manager server error failing to update data
#1 No
Has polling to the
Agent been performed? #1 Polling status check
Make sure that Main Console has performed
polling to the Agent.
Yes
No
Are Checks A#2 and
B#3 applicable? #2 Check A (Polling setting check)
Make sure that scheduled polling is set up in Main
Yes Console. See 2.4.2.1.
Satisfy the requirements in Checks A and B. #3 Check B (Checking the polling target Agent)
Make sure that the Data Polling window of Main
Console displays Agent. See 2.4.2.2.
Does Main Console No

#3
recognize the Agent?
Yes Does Collection Manager Yes

#4
recognize the Agent?
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.
Go to the next page.

1
Yes
Is polling to
Agent#6 successful?
No Is Check D#7 No
applicable?
Are Check E#8 Yes
applicable? Yes
Satisfy the requirement in Check C, E. Satisfy the requirement in Check D.

No
Perform polling#5, #6.

Check the Agent and its record/field
name which corresponds to metric of
Main Console, that is now shown as n/a.
To check, please use Appendix2 list of
No metric.xls.
Does n/a appear for
a metric?
End
Yes
Yes
#12
Is Check F#9,
Collect the logs. applicable?
End
No
No Collect the logs.#10
Has Agent Store
started?
See 2.3.3.2. Contact the support center
Yes and ask for investigation.
No #6 Checking the result of polling

Has Agent Collector In Main Console, open the Polling Details window, and
started? check the Last Recorded Time field for each Agent to
determine whether polling for the Agent was performed
See 2.3.3.1. correctly.
Yes For details, see 2.4.2.3.
No
Can PR display a #7 Check D (Report Window check)
real-time report? In Main Console, make sure that the display setting in
Report Window is specified so that only the data that
See 2.4.4.1. exists in InterBase or HiRDB is displayed.
Yes For detail, See 2.4.2.5.
Go to the next page.

#8 Check E (Checking the time difference between Tuning
2 Manager server and Agent)
Make sure that the time is the same between the host
running Tuning Manager server and the host running the
Agent.
See 2.4.5.1..
Collect the logs.#12
#10 About the logs

Contact the support center Obtain the logs for Main Console, HBase,
and ask for investigation. InterBase/HiRDB, Collection Manager, and the Agent for
which n/a is displayed for data.
We recommend you use the jpcras and hcmdsgetlogs
commands to collect maintenance information.
#9 Check F (Checking metric is supported or not) For details about how to use the jpcras command, see
Check whether metric is supported or not by using 4.1.1. hcmdsgetlogs command.
Agent Manual.
Figure 2.4-1 Tuning Manager server error causing n/a display for data flow
2.4.1. Error analysis using Main Console(Ver.5 or earlier)


2.4.2. Error analysis using Main Console(Ver.6 or later)
2.4.2.1. Checking the polling setting
Make sure that scheduled polling for Agent is set up in Main Console. Since the user must
manually set scheduled polling in Main Console, a problem of concern is that the users may forget to
set it.
Note: By default, polling is set to start at 00:00 (local time of the installation server).
Figure 2.4.2.1-1: Checking the Edit General Polling Settings window
2.4.2.2. Checking the polling target Agents

Agents recognized by Main Console are displayed in the Data Polling window. Main Console polls
those Agents. Make sure that Agents appear in this window.
Note: If Data Polling window does not display Agents, click the Refresh button.
Refresh button

Figure 2.4.2.2-1: Refreshing the Data Polling window

2.4.2.3. Checking the polling results
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-1: Selecting a Polling Time in the System Reports window
If polling has not been successful yet, Not yet
recorded appears.
Figure 2.4.2.3-2: Checking the Last Recorded Time in the Polling Details window

2.4.2.4. Checking the Configuration Status field
See the following manual:
- In Ver.6
Preparation for performing polling
- In Ver.7
- In Ver.8
2.4.2.5. Checking the Report Window settings

In Main Console, you can change the Report Window settings to display data of the specified past
time, or display aggregated data on an hourly, daily, weekly, monthly, or yearly basis.
By default, Main Console displays the latest hourly record stored in HiRDB. If Main Console does
not display data, make sure that data of the time not contained in HiRDB is not specified.
The following shows an example of correcting an error by changing the Report Window settings.
Example
Problem:
An attempt to display daily data for the USP for December 9 in 2004 failed.
Cause:
The Last Recorded Time field for the RAID Agent monitoring the USP displays 2004/12/08
23:00. When the Report Window setting is changed to display daily data for December 8 in
2004, the data is displayed.
2.4.3. Error analysis using the jpcctrl list command

In Main Console, the Data Polling window displays Agent registered in a Collection Manager
service called Master Manager. If Agents are not recognized by Main Console, make sure that
Collection Manager recognizes them.
Use the jpcctrl list command to check whether Service ID of Agent is shown, that means that
Collection Manager recognizes Agents. The following shows an example of executing the jpcctrl list
command.
- In Windows
jpcctrl list * host=*
- In Unix (Linux, Solaris)
jpcctrl list "*" host="*"
Note: To execute the jpcctrl list command in a Unix system, you need to enclose an asterisk (*) in

double quotation marks (").
If Collection Manager does not recognize Agents, check whether Agent is running Stand Alone
mode or not. For details, see 2.3.3.3. Error during connection between Collection Manager and
Agent.
2.4.4. Error analysis using PR reports

The following describes how to analyze an error using PR reports. If Main Console displays n/a for
metrics, a PR report is helpful in determining whether the problem occurs in the Agent or Tuning
Manager server. For details about the Agent's records and field names that correspond to the metrics
that Main Console displays, see Appendix 1 List of metric.
2.4.4.1. Error analysis using real-time reports

The data displayed in a real-time report is passed using a route between PR and Collection Manager
(View Server), and between Collection Manager (View Server) and Agent Collector.
If you attempt to display a real-time report but cannot collect data, an error shown in Table
2.4.4.1-1 may have occurred.
Table 2.4.4.1-1: Causes of errors when a real-time report cannot be displayed
No. Error Remarks
1 The Agent Collector service has stopped. See 2.3.3.1.
2 The Agent Collector service is running, but has failed to collect data from the See 2.4.5.2.
resources being monitored.
3 A communication error occurred in the environment in which Tuning Manager
server runs.
4 The communication error occurred between Collection Manager (View Server)
and Agent Collector.
The following shows an example of error isolation using real-time reports.

Example
Background:
Main Console does not display data for instance Lightning A. Main Console displays data for
instance Lightning B. You want to make sure that Agent has collected data for Lightning A.
Method:
Use PR to display Agent real-time data for instance Lightning A.
Data for the port is stored in the following records:
- Configuration information for the port: RAID Agent/PD_PTC record
- Performance information for the port: RAID Agent/PI_PTS record
Create and display a report showing the PD_PTC and PI_PTS records.
Result:
An attempt to display a report for Lightning A failed. A report for Lightning B was displayed
normally.

Error isolation:
An error shown in No. 1 or 2 or 4 in Table 2.4.4.1-1 may have occurred.
2.4.4.2. Error analysis using historical reports

The data displayed in a historical report is passed using a route between PR and Collection Manager
(View Server), and between Collection Manager (View Server) and Agent Store.
If you attempt to display a historical report but cannot collect data, an error shown in Table
2.4.4.2-1 may have occurred.
Table 2.4.4.2-1: Causes of errors when a historical report cannot be displayed
No. Error Remarks
1 The service of Agent Store has stopped. See 2.3.3.2.
2 The service of Agent Store stopped during the period of time for See 2.3.3.2.
which you attempted to display data in the report.
3 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, a
Agent Collector stopped. historical report is also not
output when there is a
delay in saving data to the
Store database. When there
is such a delay, the
KAVE00166-W message is
output to a log. To
determine the cause of the
delay, see the message in

the log.
4 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 A communication error occurred in the environment in which
Tuning Manager server runs.
6 The communication error occurred between Collection Manager
(View Server) and Agent Store.
The following shows an example of error isolation using historical reports.

Example
Background:
There is a period of time during which data for instance Brocade A is not displayed.
When a graph showing the number of bytes received at the Brocade switch is displayed in Main
Console, n/a appears for the data of the period of time from 13:00 in December 7, 2004 to
08:00 in December 8, 2004. You need to check whether the data of this period of time is stored
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.
2.4.5. Other considerations

2.4.5.1. Checking time difference between Tuning Manager server and Agent
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.
Tuning Manager pdoducts running on host B: Agent B

System clock of host B: 2004/12/08 12:50
Tuning Manager server on host B 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

did not display data of Agent B running on host B.
The second polling was performed when the system clock of host A reached 2004/12/08
14:00. After the polling finished, Main Console displayed data of both Agent A running on
host A and Agent B running on host B.
Description of the operation

Tuning Manager server is designed to discard the latest record of the data collected from
Agent, because there is possibility that aggregation is not completed for the latest record of
PI type in Agent.
The first polling collected the following records from 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 is
incomplete.)
Host B: Records at 2004/12/08 12:00 (Data aggregation for the PI-type record completed.)
Note: Since the host B clock did not reach 13:00 at the first polling, a record of
13:00 did not exist in Agent Store.
As a result, the records at 2004/12/08 12:00 collected from Agent A on host A are stored in
InterBase or HiRDB during the first polling.
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.)
incomplete.)
Host B: A record of 2004/12/08 12:00 (Data aggregation for the PI-type record
completed.)
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.
The following describes how to prevent this problem.

Plan: Set the system clock of the host running Agent to the time of the system clock of the host
running Tuning Manager server.
You can use the NTP protocol to set the clock of a host on the network.

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.

2.5. Errors in Tuning Manager API
Main errors and assumed factors when using Tuning Manager API are shown below.
# Symptom Assumed factors

1 Refresh process of Agent (1) If there is KATR11002-E output in the message log;
information fails. 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".
2 Refresh process of agent (1) Check the service status of HTnM-Agent REST Web
information succeeded but even if service, HTnM-Agent REST Application service, or Agent
the agent information is received, Collector service in the host which the agent is not
there is no update of last update updated. If either of the services is stopped, start the
time of each agent (time remains service.
or null remains).
3 Cannot obtain performance data (1) Try the same action of #2 (1) above.
(2) Performance data is not obtained immediately after Agent
Collector service was started or immediately after creating
agent instance. For PD series record, obtain again after 00
minute of an hour. For PI series record, obtain again after
collection interval set for each record.
(3) If you are trying to obtain performance data of an
unsupported record of monitored storage, empty csv file
will return (with header) or HTTP status will be 404.
Ensure to obtain performance data of supported record.
(4) Check if the performance data is not obtaining from non
existing agent. Obtain the agent instance list by Tuning
Manager API and access an agent instance in the agent
instance list.
(5) If you cannot obtain performance data when performance
data is collected via a TCP/IP connection, see 7.15 for a
solution.
4 Created agent instances cannot be (1) There is a possibility that it is not recognized by managed
found in the instance list obtained target of HTnM REST Application Service. Execute
by Tuning Manager API. refresh process of Tuning Manager API agent information
and then recheck the instance list.
(2) If you cannot find NAS Agent instances in the instance list
obtained by Tuning Manager API, the data storage format
of the NAS Agent might be Store database. To use the

Tuning Manager API for NAS Agent, the data storage
format must be Hybrid Store. If the data storage format of
the NAS Agent is Store database, change it to Hybrid
Store.
5 Deleted agent instances are found (1) There is a possibility of management information HTnM
in the instance list obtained by REST Application Service is old. Please refresh the agent
Tuning Manager API. information in the Tuning Manager API.
(2) There is a possibility that the Agent Collector service is
not deleted or Collector Manager and Performance
Reported are not restarted after deleting the service. Delete
the instance by referring to the manual. In addition, after
deleting instance, refresh the agent information in Tuning
Manager API.
2.6. Errors when using the alert function

Main errors when using the alert function, and their possible causes, are shown below.
# Symptom Assumed factors

1 No alerts are issued. (1) There is a possibility that communication between the
agent host and the SMTP server cannot work correctly
when KATR13257-E, KATR13258-E, KATR13264-, or
KATR13264-I is output to the message log. Check the
host name (IP address) and network for the specified
SMTP server and establish proper communication
between the agent host and the SMTP server.
(2) If KATR13261-E or KATR13262-E is output in the
message log, an incorrect property is specified. Rewrite
the property value, and then restart HTnM - Agent REST
Application Service.

3. Information for Troubleshooting
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.
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.
For an error in Switch Agent, acquire the following information:

(12) Information about the Brocade switch (B-Model) and Brocade switch (M-Model). For the list of
log files to be collected, see 4.2.3. Switch Agent.
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

4. RAS Collection
4.1. RAS information collection commands
Table 4.1-1 lists the products and commands for collecting RAS information of Tuning Manager
server.
Table 4.1-1: List of products and applicable RAS information collection commands
Product hcmdsgetlogs htm-getlogs htm- jpcprras jpcras hinstgetlogs
earlier V7.0 to V8.0 earlier V7.0 to V8.0 dump V8.1.4 or
than earlier or than earlier or later
V7.0 than 8.0 later V7.0 than 8.0 later
Main Console Y Y Y Y Y Y Y N N N
Performance Reporter Y Y Y Y Y Y N Y N N
Tuning Manager Server
Tuning Service#3 Y Y Y#4 Y Y Y#4 Y N N N
HBASE Y Y Y Y#1 Y#1 Y N Y#1 N N
HiRDB Y Y Y N Y Y N N N N
Collection Manager Y Y Y Y Y Y N N Y N
Installer Y Y Y Y Y Y Y N N Y
Agent Collector Y Y Y Y Y Y N N Y N
Agent
Agent Store Y#2 N N Y#2 N N N N Y N
Installer Y Y Y Y Y Y N N Y N
Hitachi Storage Command Y Y Y N N N N N N N
Suite products other than
Tuning Manager server
(such as HDvM)
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 Information is collected only if a Tuning Service directory exists.

4.1.1. hcmdsgetlogs command
(1) Overview
The hcmdsgetlogs command collectively acquires RAS information, database information, and other
information about all the Hitachi Storage Command Suite products (HTnM, HDvM, HPcM, HDLM,
HPtM, HPvM, HGLAM, HBASE, and InterBase/HiRDB) running on the host.
Notes (Ver.6.4 or later)
The log files collected by the hcmdsgetlogs 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.
- RAS information acquisition fails due to insufficient free disk space.
- 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:

# <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:
> "C:\Program Files\HiCommand\Base\jdk\bin\jar.exe" -xvf path-name
> "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.
- Note on the hcmdsgetlogs command of Tuning Manager server for Windows

If the KAPM05318-I or KAPM05319-E message is not displayed when the hcmdsgetlogs
command ends, the command has been interrupted due to insufficient space in the output
destination folder for maintenance information. Allocate sufficient space in the output
destination folder for maintenance information, and then re-execute the command.
(4) How to estimate the required capacity for executing hcmdsgetlogs

(4.1) Purpose
Because the hcmdsgetlogs command is used to collect log files and database files together, it

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
1 HiCommand_log.jar Log file, Store database file of Agent
2 HiCommand_log.hdb.jar Log file of HiRDB
3 HiCommand_log.db.jar Database file
4 HiCommand_log.csv.jar Table database file
Before compression, the HiCommand_log.jar size is estimated as [A], the

HiCommand_log.hdb.jar size is estimated as [B], the HiCommand_log.db.jar size is
estimated as [C], and the HiCommand_log.csv.jar size is estimated as [D]. Finally, the total
capacity is calculated for the log destination required by the common component, HiRDB, and
HTnM for when [A], [B], [C] and [D] are used to execute the hcmdsgetlogs command.
(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 [ In Ver.6 to earlier than 8 ]
For Windows Server 2003 (x86), and Windows Server 2008
(x86)
%SystemDrive%\Program Files\HiCommand\Base
1 For Windows Server 2003 (x64), Windows Server 2008 (x64)
and Windows Server 2012
%SystemDrive%\Program Files (x86) \HiCommand\Base
%SystemDrive%\Program Files\HiCommand\Base64
Tuning-Manager-server-installation-directory [ In Ver.6 to earlier than 8 ]
For Windows Server 2003 (x86) and Windows Server 2008
2 (x86)
%SystemDrive%\Program Files\HiCommand\TuningManager
For Windows Server 2003 (x64), Windows Server 2008 (x64)

and Windows Server 2012
%SystemDrive%\Program Files
(x86)\HiCommand\TuningManager
%SystemDrive%\Program Files\HiCommand\TuningManager
[Note] Above directory is the default directory for the installation.
(4.4) Formula for estimating the free space required to execute the hcmdsgetlogs command
The following formula is used to estimate the free space required.
Table 4.1.1-3: Formula for estimating the free space required to execute the hcmdsgetlogs
command
Calculating formula
The free space required to execute the hcmdsgetlogs command = Max { [A], [B], [C] } + ( [A] + [B] +
[C] + [D] ) * 0.2
* Max {[A], [B]. [C].} indicates that the largest size among [A], [B], and [C] is selected.
Substitute the following sizes for [A], [B], [C], and [D] respectively:
Variable Value substituted Calculation
Procedure
[A] HiCommand_log.jar size before compression See (4.5)
[B] HiCommand_log.hdb.jar size before compression See (4.6)
[C] HiCommand_log.db.jar size before compression See (4.7)
[D] HiCommand_log.csv.jar size before compression See (4.8)
(4.5) Estimating the HiCommand_log.jar size before compression

The following formula is used to estimate the size.
The following method is used to confirm the directory size.
For Windows: Confirm size by displaying the directory property in Explorer.
For UNIX: Confirm size by using the df -k "Directory Path" command.

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.
Procedure
[a] The size of the common component, the HTnM Install directory, and other See (4.5.1)
directories
[b] System Log size See (4.5.2)
[c] Watson Log size See (4.5.3)
[d] The size of RAS information for the Agent for RAID, installed on the same See (4.5.4)
host where Tuning Manager server is installed.
[e] The size of the database used by the common component See (4.5.5)
[f] The size of the installation directories for HiRDB and jdk See (4.5.6)
[g] The size of the database used by Tuning Manager See (4.5.7)
[h] The size of the backup files for CollectionManager and Agent 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
1 Common-Component-installation-directory
2 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 Logic host environment directory
# Solaris
1 /opt/HiCommand/Base
2 /var/opt/HiCommand/Base
3 /opt/HiCommand/TuningManager
4 /var/opt/HiCommand/TuningManager
5 /opt/jp1pc (*1)
6
/opt/HiCommand/TuningManager/PerformanceReporter/log)

# Linux
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>
2 /var<Hitachi-Command-Suite-Common-Component-Installation-directory>
3 <TuningManager-Installation-directory>
4 /var<TuningManager-Installation-directory>
5 /opt/jp1pc (*1)
6
<TuningManager-Installation-directory>/PerformanceReporter/log)
* 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) Estimating [b]: the system log size

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.
(4.5.2-1) For Windows

<Step1> Execute Start, Control Panel, Administrative Tools, and then Event Viewer to start
Event Viewer.
<Step2> Confirm the size of all the logs shown by Event Viewer in the Property dialog box.

Figure 4.1.1-1 Event Viewer
Figure 4.1.1-2 Property dialog box
<Step3> [b] represents the total sum of the log sizes

Note: Depending on the environment, the size might decrease or increase by about 50%. If you
require a more accurate figure, you can use the size of the event logs when they are saved in
text format to estimate.

(4.5.2-2) For Solaris
<Step1> [b] indicates the total sum of the following file sizes:
Table 4.1.1-6: System logs collected by Solaris
# Files
1 /var/adm/messagesX *1
(*1) The last character X indicates the number.
(4.5.2-3) For Linux

<Step1> [b] indicates the total sum of the following file sizes:
Table 4.1.1-6-1: System logs collected by Linux
# Files
1 /var/log/messages[.X]
(*1) The last character X indicates the number.
(4.5.3) Estimating [c]: the size of the Watson log

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
# Files
1 %userprofile%/Local Settings/Application Data/Microsoft/Dr Watson/drwtsn32.log
2 %userprofile%/Local Settings/Application Data/Microsoft/Dr Watson/user.dmp
(4.5.4) Estimating [d]: the size of RAS information for the Agent for RAID
[d] indicates the result of the following calculation:
Calculating formula
[d] = (Number of DF instances constructed on the same host as the Tuning Manager server) * 80MB +
(Number of RAID instances constructed on the same host as the Tuning Manager server) * 50MB
(4.5.5) Estimating [e]: the size of database used by the common component
Confirms the size directory, which is the destination of database file used by the common
component.
(4.5.5.1) Open the command prompt.
(4.5.5.2) Execute the hcmdsdbpath command.
[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]
/opt/HiCommand/Base/bin/hcmdsdbpath
[For Linux]
<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
[f] indicates the total sum of the following directory sizes:
Table 4.1.1-8: Installation directories for HiRDB and jdk
# Windows
1 Common-Component-installation-directory\HDB
Common-Component-installation-directory\jdk
2
Common-Component-installation-directory\uCPSB\jdk
3 Common-Component-installation-directory\jdk1_4_02
# Solaris
1 /opt/HiCommand/Base/HDB
2 /opt/HiCommand/Base/jdk
# Linux
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
2 <Hitachi-Command-Suite-Common-Component-Installation-directory>/jdk

<Hitachi-Command-Suite-Common-Component-Installation-directory>/uCPSB/jdk
(4.5.7) Estimating [g]: the size of the database used by Tuning Manager
Confirms the size of the database used by Tuning Manager.
(4.5.7.2) Execute the htm-db-status command.
[For Windows]
Tuning-Manager-server-installation-directory\bin\htm-db-status
[For Solaris]
/opt/HiCommand/TuningManager/bin/htm-db-status
[For Linux]
<TuningManager-Installation-directory>/bin/htm-db-status
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) [g] indicates the result of the following calculation:

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
1 Tuning-Manager-server-installation-directory\jp1pc\mgr\store\backup
2 Tuning-Manager-server-installation-directory\jp1pc\<Service Key of Agent>\store\backup
Tuning-Manager-server-installation-directory\jp1pc\<Service Key of Agent>\store\<Instance

3
Name>\backup

# UNIX
1 opt/jp1pc/mgr/store/backup
2 opt/jp1pc/<Service Key of Agent>/store/backup
3 opt/jp1pc/<Service Key of Agent>/store/<Instance Name>/backup
(4.6) Size [B] of HiCommand_log.hdb.jar before compression

The following formula is used to estimate the size:
Table 4.1.1-10: Formula for estimating the size [B] of HiCommand_log.hdb.jar
Calculating formula
[B] = [i] + [j]
* Substitute the following sizes for [i] and [j], respectively:
Procedure
[i] The total sum of the capacities indicated by the pdinfoget -m command See (4.6.1)
[j] Event log size See (4.6.2)
(4.6.1) Estimating [i]: the total sum of the capacities indicated by the pdinfoget - m command
(4.6.1.2) Set the environmental variables
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
1 cd /d "Common-Component-installation-directory\HDB\bin"
2 pdntcmd
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
# Command
1 set PDDIR
(4.6.1.2-2) For Solaris

Depending on the type of shell, how to set the environmental variable differs.
# Environment variable name Value
1 PDDIR /opt/HiCommand/Base/HDB

2 PDCONFPATH /opt/HiCommand/Base/HDB/conf
3 LD_LIBRARY_PATH /opt/HiCommand/Base/HDB/lib
4 PATH /opt/HiCommand/Base/HDB/bin
# kind of shell A example of a setting of the environment variables
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
PATH=/opt/HiCommand/Base/HDB/bin:$PATH
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
export PATH
3 csh or tcsh setenv PDDIR /opt/HiCommand/Base/HDB
setenv PDCONFPATH /opt/HiCommand/Base/HDB/conf
setenv LD_LIBRARY_PATH /opt/HiCommand/Base/HDB/lib
setenv PATH /opt/HiCommand/Base/HDB/bin:${PATH}
4 Shell other than the above refer to the manual of each shell.
command
# Command
1 env | grep PDDIR
Display result
PDDIR=/opt/HiCommand/Base/HDB
(4.6.1.2-3) For Linux(Ver.7.1 or later)

# Environment Value
variable name
1 PDDIR <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
2 PDCONFPATH <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/conf
3 LD_LIBRARY_PATH <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib
4 PATH <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin

# kind A example of a setting of the environment variables
of
shell
1 bash source <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pduxenv
2 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 PATH
3 csh setenv PDDIR <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
or setenv PDCONFPATH
tcsh <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/conf
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 refer to the manual of each shell.
other
than
the
above
command
# Command
1 env | grep PDDIR
Display result
PDDIR=<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
(4.6.1.3) Execute the command indicated below.

# Command
1 pdinfoget -m
(4.6.1.4) [i] indicates the total sum of the values for the init_directory and
detail_directory.

Output example
KFPN10400-I Pdinfoget started
init_directory = 41 Mbyte
detail_directory = 935 Mbyte
KFPN10401-I Pdinfoget terminated, return code=0
(4.6.2) Estimating [j]: the size of the event log

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.2) Execute the htm-db-status command.
[For Windows]
Tuning-Manager-server-installation-directory\bin\htm-db-status
[For Solaris]
/opt/HiCommand/TuningManager/bin/htm-db-status
[For Linux]
<TuningManager-Installation-directory>/bin/htm-db-status
(4.7.1.3) The total value indicated in the command execution result represents the total
capacity of the databases that are used by Tuning Manager.
Output example
Area Path:
C:\Program Files\HiCommand\TuningManager\database\TuningManager\TM00
(4.8) Estimating [D]: the HiCommand_log.csv.jar size before compression

The following formula is used to estimate the size:
Calculation formula
[D] = (Tuning Manager database usage) * 0.7
(4.8.1) Confirming Tuning Manager database usage

The value for "Used" in (4.7.1.3) indicates Tuning Manager database usage.
4.1.2. htm-getlogs command

(1) Overview
The htm-getlogs command collectively acquires RAS information, database information, and other
information about all Tuning Managers(Main Console/HBASE/Collection Manager/Performance
Reporter/Agent) except for
HiRDB running on the host.
Note: If you want to gather all Tuning Manager server log files including HiRDB, please use
hcmdsgetlogs command with [/type Tuning Manager] option.
The following shows the types of acquired information and the locations of the files that contain
the acquired information:
[In Ver.6.3 or earlier, or Ver.6.4 (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/
[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

installed on a same host, please execute jpcras command after executing htm-getlogs command.
(2) Prerequisites
installed.
- You do not need to stop the Tuning Manager server services.
must be stopped.
(3) Use
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
Specify the -z option to compress the RAS information.
4.1.3. htm-dump command

(1) Overview
The htm-dump command collectively acquires RAS information, database information, and other
information about Main Console, InterBase running on the host. Note that this command does not
acquire the RAS information about HiRDB, HBASE, Collection Manager, Performance Reporter,
or Agent.
If you execute the command with -z option, following file is created which contains and
compressed above files.
Execution results of htm-dump command with -z option: specified-directory/HTM.zip
(2) Prerequisites
installed.
- You do not need to stop the Tuning Manager server services.

must be stopped.
(3) Use
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
Specify the -z option to compress the RAS information.
4.1.4. jpcprras command

(1) Overview
The jpcprras command collectively acquires the log files of HBASE or Performance Reporter
running on the host. Note that this command does not acquire the log and database information
about Main Console, HiRDB, Collection Manager, and Agent.
It is recommended that you use this command to collect maintenance information when the cause
of the error can be located in Performance Reporter or HBASE.
(2) Prerequisites
installed.
(3) Use
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

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.
4.1.5. jpcras command

(1) Overview
The jpcras command collectively acquires the log files of Collection Manager and Agent running
on the host. Note that this command does not acquire the log and database information about Main
Console, Interbase/HiRDB, HBASE, and Performance Reporter.
It is recommended that you use this command to collect maintenance information when the cause
of the error can be located in Agent (for example, when the Agent data is not collected).
(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 Collection Manager or Agent is
installed.
- This command cannot acquire the log files of Collection Manager or Agent running on
a remote host.
If you want to acquire the log files of Agents installed on multiple hosts, you must execute the
jpcras command on each host.
- Before acquiring the information about the Agent database of Tuning Manager server, make
sure that the Agent services are stopped.
(3) Use
To use the jpcras command to acquire the log of a specific product, specify the service key or
instance name of the product as an argument of the command.
Table 4.1.5-1 lists the service keys of Collection Manager and Agent products.
Table 4.1.5-1: Service keys of Collection Manager and Agent products

No. Service key Product
1 mgr Collection Manager
2 agtd RAID Agent

3 agte RAID Map Agent
4 agtm EAP Agent
5 agtn NAS Agent
6 agto Oracle Agent
7 agtq SQL Agent

8 agtr DB2 Agent
9 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 Health Check Agent
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):
# 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):
# jpcras /export/Logs agtd all inst=LightningA
4.2. RAS information manually collected

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.
4.2.1 Installation log files(Ver.5 or earlier)
4.2.2 Installation log files(Ver.6 or later)

[1] Installation/Uninstallation failure
Please get following log files manually.
[For Tuning Manager server]

Refer to the section Handling errors of the following manual:
- In Ver.6
- In Ver.7
- In Ver.8
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:
[Output destination example]

The environment variable %TEMP% value obtained by using the GUI:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
The environment variable %TEMP% value obtained when a remote desktop connection is used
for a remote session:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1 (*1)
(*1) The folder "\1" is automatically generated when you login and deleted when you log off.
When an additional connection is established for a remote session, an additional folder
(such as "\2" or "\3") is automatically generated and assigned to the session.
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

you log off.
When you use the remote desktop function to operate Tuning Manager, connect to a console
session on the destination server as described in the manual.
[For Agent]
Refer to the section, Collecting information if an installation failure occurs of the following
manual:
- In Ver.6
- In Ver.7
- In Ver.8
[2] RAS command cannot be used

If the hcmdsgetlogs command cannot collect log data for Tuning Manager, and the hinstgetlogs
command cannot be used, refer to the section Handling errors of the following manual:
- In Ver.6
- In Ver.7
- In Ver.8
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 File Name Log Location OS Installed PP
1 All files and Suite-installation-directory\TuningManager Windows Tuning Manager
directories under \jp1pc server,
Log Location Agents
/opt/jp1pc UNIX Tuning Manager
server,
Agents
2 Eventlog - Windows Tuning Manager
(application), server,
Eventlog(system) Agents
3 Syslog Default Location: UNIX Tuning Manager
- Case HP-UX server,
/var/adm/syslog/syslog.log Agents
- Case Solaris

/var/adm/messages*
- Case AIX
/var/adm/syslog*
- Case Linux
/var/log/messages*
4 All log files described in the section All Agents
Data collected in the event of an error of The following

manual:
- In Ver.6
- In Ver.7
Hitachi Command Suite Tuning Manager Software
Installation Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Installation
Guide

4.2.3 Switch Agent
For Switch Agent, in addition to the data acquired using the RAS information collection commands
described in 4.1.5, you need to acquire the monitored resources information manually.
(1) JavaVM information

For the Switch Agent using SMI-S IF, the following JavaVM information is required when
JavaVM abnormally ended.
- 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 JavaVM is
Agent used?
Brocade 6.0 or later *1 Windows SMI-S Yes
6.1 or later *2 Solaris SMI-S Yes
McDATA 6.2 or later Windows SMI-S Yes
6.2 or later Solaris SMI-S Yes
CISCO 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.

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 JavaVM is
Agent 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
Brocade(SMI Agent for 7.1 or later Windows SMI-S Yes
FOS) 7.1 or later Solaris SMI-S Yes
Brocade(SMI Agent for 7.1 or later Windows SMI-S Yes
EOS) 7.1 or later Solaris SMI-S Yes
CISCO(Seed Switch) 7.1 or later Windows SMI-S Yes
7.1 or later Solaris SMI-S Yes
CISCO(DCNM-SAN SMI-S 7.2.1 or later Windows SMI-S Yes
Agent)
7.2.1 or later Solaris SMI-S Yes
7.2.1 or later Linux SMI-S Yes
(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.
(3)When switches are monitored

(3.1) For Brocade(DCFM SMI Agent) (7.1 or later)
(A) Please collect detailed log in to DCFM Server from DCFM Client, and then acquire the
following logs(When you acquire the logs, the license of DCFM will be required):
- Audit Log
- Event Log
- Fabric Log
- FICON Log
- Product Status Log
- Security Log
- Syslog Log
- Technical Support Information

(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 The command name used for getting log files
the monitored Brocade switch
V4.4.0b or earlier 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

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 Information output Usage

Level 1 Timestamps only Investigation of ordinary
failures
Level 2 All data, including Investigation of failures
communication data that require action on the
FC switch side
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
(1) Applicable versions of Agent for SAN Switch
- HTnM - Agent for SAN Switch version 7.1.0-00 or later (Windows/Linux)
- HTnM - Agent for SAN Switch version 7.1.0-00 to earlier than 8.0.0 (Solaris)
(2) Applicable versions of DCFM
- DCFM 10.4.0 or later
1
3. Notes
When you collect DCFM SMI Agent supportsave data, and detailed XML trace log
data, note the following:
(1) When you collect debug log data and detailed XML trace log data, you must change
the configuration beforehand with the procedures described in 4. Preconfiguration
Required for Collecting Supportsave Data and Detailed XML Trace Log Data.
(2) You do not need to change the DCFM SMI Agent configuration when collecting audit
log data because DCFM SMI Agent collects audit log data by default.
(3) To collect supportsave 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 DCFM SMI Agent 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 DCFM SMI
Agent 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 Supportsave Data and Detailed XML

Trace Log Data
To collect supportsave data, you must change the configuration by using DCFM.
To output detailed XML trace log data, you must manually change the values set for
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.
2
certain properties defined in the following file:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
4.1. Stopping the Agent for SAN Switch instance

(1) Starting the console
- In Windows:
From the Start menu, choose All Programs, Accessories, and then Command
Prompt to start Command Prompt. (The following figure shows a Windows 2008
Server screenshot).
Figure 4.1-1 Starting Command Prompt
When Command Prompt starts, the following window appears.
3
Figure 4.1-2 Command Prompt window
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
/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 *
/opt/jp1pc/tools/jpcctrl list *
4
4.2. supportsave data configuration
In the case of monitoring Brocade switch(B-Model), you need to acquire supportsave
data.
If you do not have the license of DCFM, acquire the supportsave data by executing
SupportSave commands for each switches.
If you have the license of DCFM, acquire the supportsave data by the following
procedure.
[Procedure when you have the license of DCFM]

(1) Starting Server Configuration Tool
- In Windows:
From the Start menu, choose All Programs, DCFM 10.4.x, and then DCFM 10.4.x to
start DCFM server. (The following figure shows a Windows 2008 screenshot).
Figure 4.2-1 Example of starting Server Configuration Tool
Start DCFM server by executing the following command from the console:
cd DCFM-installation-directory/bin
./dcfm
5
(2) Logging in to Server Configuration Tool
When Server Configuration Tool starts, the login window is displayed. In the login
window, enter your user ID and password and then click the Login button.
Figure 4.2-2 DCFM Server login window
(3) In the DCFM menu, click Monitor, Technical Support, and then Switch / Host SupportSave.
Figure 4.2-3 Window for collecting supportsave data
6
(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.
7
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.
4.3. Technical Support Information

(1) Starting Server Management Console
- In Windows:
From the Start menu, choose All Programs, DCFM 10.4.x, and then Server
Management Console to open Server Management Console.
Open Server Management Console by executing the following command from the
console:
cd DCFM-installation-directory/bin
./smc
(2) DCFM Server Console is opened, and then choose Technical Support Information
tab.
(3) Set an output path to Output Path for collecting materials.
8
Figure 4.3-1 Server Management Console
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.
Open the /opt/jp1pc/agtw/agent/instance-name/jpcagt.ini file using an editor.
9
Figure 4.4-1 jpcagt.ini file (for Windows, before setting changes)
(2) Changing the values of properties related to XML trace log

In the [Agent] section, change the property values as follows:
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2
10
Figure 4.4-2 jpcagt.ini file (for Windows, after setting changes)
(3) Saving the settings

After you make the changes, save the settings, and then close the jpcagt.ini file.
4.5. Starting 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 start the instance.
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstart agtw inst=instance-name
/opt/jp1pc/tools/jpcstart agtw inst=instance-name
11
5. Collecting Detailed XML Trace Log Data
This chapter describes how to collect detailed XML trace log data.
5.1. Collecting information by executing the jpcras command

To collect information, execute the jpcras command as follows:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcras
path-to-directory-where-maintenance-information-is-stored agtw all
/opt/jp1pc/tools/jpcras
(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.
Figure 5.1-1 Display when maintenance information collection starts
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
6. Procedure for Restoring the Environment

When collection of detailed XML trace log data is complete, perform the following
procedure to restore the original configuration.
6.1. Restoring the detailed XML trace log configuration

Open the jpcagt.ini file using a text editor.
- In Windows:
Change the [Agent] section as follows:
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1

6.2. Deleting XML trace log data

The next step is to delete the detailed XML trace log data.
Delete the following file:
13
Detailed XML trace log output directory:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
/opt/jp1pc/agtw/agent/instance-name
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:
-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).

failures
Level 2 All data, including Investigation of FC
communication data switch failure, which
requires additional data
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
XML trace log data).
This document describes how to collect CIMOM log data, provider log data and
detailed XML trace log data.
2. Prerequisites
- Version of Agent for SAN Switch:
- 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
- Version of SMI Agent for FOS:
- SMI Agent for FOS 120.6.0a (Windows/Solaris/Linux)
- SMI Agent for FOS 120.7.1 (Windows/Solaris/Linux)
1
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
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
Restoring the Environment.
(6) 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.
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
2
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
- In Windows:
3
(1) Starting Command Prompt
- In Windows:
From the Windows Start menu, choose Programs, Accessories, and then Command
Prompt to start Command Prompt (The following figure shows a Windows 2000
Advanced Server screenshot).
4
Start the console.
(2) Stopping an instance

Stop the appropriate instance by executing the following command:
- In Windows:

Inactive).
- In Windows:
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)
4.2. Starting Brocade SMI Agent Configuration Tool

(1) Starting Brocade SMI Agent Configuration Tool
- In Windows:
From the Windows Start menu, choose Programs, SMIAgent SMI Agent for FOS
5
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
Start Brocade SMI Agent Configuration Tool by executing the following command:
SMI-Agent-for-FOS-installation-directory/agent/server/jserver/bin/configurationtool.sh
6
Menu tree
Action buttons
Server buttons
Figure 4.2-2 Brocade SMI Agent Configuration Tool Screenshot and Description of Sections
7
4.3. Configuring CIMOM log
4.3.1. Configuring CIMOM log by using SMI Agent for FOS 120.6.0a
(1) Displaying the window for configuring CIMOM log
In the Menu tree, under Debugging And Logging, choose CIMOM.
Figure 4.3-1 Window for Configuring CIMOM log of SMI Agent for FOS 120.6.0a (Before
Configuration)
8
(2) Configuring CIMOM log
Collect CIMOM log data, specify the following items:
(a) Select the Enable Debugging check box.
(b) Select File for Where do you want to write the debug output.
(c) Select 1 from the Debug Level drop-down menu.
(d) In the Log File Name text box, type the name of the file to which the CIMOM log
data will be output.
(e) Select the Enable XML Debugging check box.
(f) Select File for Where do you want to write the XML debug output.
(g) In the XML Debug File Name text box, type the name of the file to which the XML
(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)
(3)Saving the CIMOM log configuration information

Click the Apply button to save the CIMOM log configuration information.
9
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
(2) Configuring CIMOM log
Select FINE WITH XML TRACE for Select log Level.
Figure 4.3-4 Window for Configuring CIMOM log of SMI Agent for FOS 120.7.1 (After
Configuration)
(3)Saving the CIMOM log configuration information

11
4.4. Configuring Provider log
(1) Displaying the window for configuring Provider log
In the Menu tree, under Debugging And Logging, choose Provider.
Figure 4.4-1 Window for Configuring Provider log (Before Configuration)
12
(2) Configuring Provider log
Specify the following settings to collect the Provider log data:
(a) Select the Enable File logging check box.
(b) In the Log File text box, type the full path name of the file to which the provider log
(c) In the File Size (in Kilobytes) text box, enter 10240 as the size of the provider log
file.
(d) In the No. of Files text box, enter 5 as the maximum number of files for the
provider log
(a)
(b)
(c)
(d)
Figure 4.4-2 Window for Configuring Provider log (After Configuration)
(3) Saving the Provider log configuration information

Click the Apply button to save the Provider log configuration information.
13
(4) Displaying the window for specifying the Debug configuration
To specify detailed information about the Provider log, display the window for
specifying the Debug configuration.
In the Menu tree, under Debugging And Logging, choose Debug.
Figure 4.4-3 Window for Specifying the Debug Configuration (Before Specification)
14
(5) Specifying the Debug configuration
Specify the following items to set the detailed information about the Provider log:
(a) Select the Enable Debug logging check box.
(b) Select File Update.
(c) In the Debug Configuration file text box, type the full path name of the file to
which the debug configuration information will be output.
(d) Select the Exception check box.
(e) Select 2 from the Exception Level pull-down menu.
(f) Select the Operation check box.
(g) Select the Event check box.
(h) Select the Switch Data check box.
(i) Select the Switch XML Data check box.
(a)
(b)
(c)
(d)
(f) (e)
(g)
(h)
(i)
Figure 4.4-4 Window for Specifying the Debug Configuration (After Specification)
(6) Saving the debug configuration information

Click the Apply button to save the Debug configuration information.
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:
Figure 4.5-1 jpcagt.ini file before changes in Windows
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_PAGE=64
XML_TRCLOG_LEVEL=2
Figure 4.5-2 jpcagt.ini file after changes in Windows
(3) Save the settings.

17
4.6. Stopping and restarting SMI Agent for FOS
(1) Stopping SMI Agent for FOS
Click the Stop Server button to stop SMI Agent for FOS.
(2) Restarting SMI Agent for FOS

Click the Start Server button to restart SMI Agent for FOS.

Perform the procedure described in 4.1. Stopping the Agent for SAN Switch instance
to start Command Prompt. Execute the jpcstart command to start the instance.
- In Windows:
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.

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
Tool to start Brocade SMI Agent Configuration Tool.
(2) Stopping SMI Agent for FOS

Click the Stop Server button to stop SMI Agent for FOS.
19
5.4. Obtaining the CIMOM log
Obtain the CIMOM log file and XML Debug file (for SMI Agent for FOS 120.6.0a only)
specified in 4.3 Configuring CIMOM log from the following directory.
CIMOM log output directory:

- In Windows:
SMI-Agent-for-FOS-installation-directory\agent\server\jserver\bin
SMI-Agent-for-FOS-installation-directory/agent/server/jserver/bin
CIMOM log file name:
file-name-specified-as-log-file-name_[MMDD]_[hhmm]
(In the above, [MMDD] is the date when SMI Agent for FOS was started, and
[hhmm] is the time when SMI Agent for FOS was started.)
XML debug file name (for SMI Agent for FOS 120.6.0a only):
file-name-specified-as-XML-debug-file-name
5.5. Obtaining the provider log

Obtain the provider log file specified in 4.4 Configuring Provider log.
Provider log file name:
file-name-specified-as-log-file[?]
(In the above, [?] is a numeric character from 0 to 4.)
20
- In Windows:
For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.
Figure 5.6-1 Startup of maintenance information collection in Windows
21
If the following message appears, collection was successful.
Figure 5.6-2 Successful collection of maintenance information in Windows
22
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
(2) Restoring the CIMOM log configuration
Specify the following items to restore the CIMOM log configuration:
(a) Clear the Enable Debugging check box.
(e) Clear the Enable XML Debugging check box.
(a)
(b)
Figure 6.1-2 Window for Configuring the CIMOM log of SMI Agent for FOS 120.6.0a (After
Configuration)
(3) Saving the CIMOM log configuration information

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
(2) Restoring the CIMOM log configuration
Select NO LOG for Select log Level.
Figure 6.1-4 Window for Configuring the CIMOM log of SMI Agent for FOS 120.7.1 (After
Configuration)
(3) Saving the CIMOM log configuration information

26
6.2. Restoring the provider log configuration
(1) Displaying the window for specifying provider log
In the Menu tree, under Debugging And Logging, choose Provider.
Figure 6.2-1 Window for Configuring Provider log (Before Configuration)
27
(2) Restoring the Provider log configuration
Specify the following item to restore the Provider log configuration:
(a) Clear the Enable File logging check box.
(a)
Figure 6.2-2 Window for Configuring Provider log (After Configuration)
(3) Saving the provider log configuration information

Click the Apply button to save the provider log configuration information.
28
6.3. Restoring settings
- In Windows:
Change the Agent section as follows:
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1


This section describes how to delete detailed XML trace log data.
Delete the following files:

- In Windows:
Name of target files:
(In the above, [?] is a numeric value from 0 to 63.)
29
6.5. Restarting SMI Agent for FOS
Click the Start Server button to restart SMI Agent for FOS.

To start the instance of Agent for SAN Switch, perform the procedure described in 4.1
Stopping the Agent for SAN Switch instance.
-End of document-
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
- 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
- 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
(3.4) For CISCO (7.0 or earlier) or CISCO(Seed Switch) (7.1 or later)

Log in to the switch specified as Seed Switch via telnet, and acquire the execution result of the
show tech-support command.
(A) Log in to the switch specified as Seed Switch via telnet, and acquire the execution
result of the show tech-support command.
(B) please collect detailed XML trace log data by the following procedure.
How_to_collect_deta
iled_XML_TraceLog(S

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.

failures
Level 2 All data, including communication Investigation of failures
data that require action on the
FC switch side
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
(1) Applicable versions of Agent for SAN Switch
- HTnM - Agent for SAN Switch for Windows version 6.2.0-00 or later
- HTnM - Agent for SAN Switch for Solaris version 6.2.0-00 to earlier than 8.0.0
- HTnM - Agent for SAN Switch for Linux version 7.1.0-00 or later
(2) Applicable versions of SMI Agent for EOS
- Brocade SMI Agent for EOS 2.5 (Windows/Solaris)
- Brocade SMI Agent for EOS 2.7 (Windows/Solaris)
3. Notes
When you collect SMI Agent for EOS audit log data, debug log data, and detailed
1
XML trace log data, note the following:
(1) When you collect debug log data and detailed XML trace log data, you must change
the configuration beforehand with the procedures described in 4. Preconfiguration
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
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
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
2
- In Windows:

(1) Starting the console
- In Windows:
From the Start menu, choose Programs, Accessories, and then Command Prompt to
start Command Prompt. (The following figure shows a Windows 2003 Server
screenshot).
3
Start the console.
(2) Stopping the instance

Stop the instance by executing the following command:
- In Windows:

Inactive).
- In Windows:
4
4.2. Starting Server Configuration Tool
- In Windows:
From the Start menu, choose Programs, SMI_Agent_for_EOS_products_2.5 or
SMI_Agent_for_EOS_products_2.7, and then Server Configuration Tool to start
Server Configuration Tool. (The following figure shows a Windows 2003 screenshot).
Figure 4.2-1 Example of starting Server Configuration Tool
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
(2) Logging in to Server Configuration Tool

When Server Configuration Tool starts, the login window is displayed. In the login
window, enter your user ID and password and then click the Login button.
5
Figure 4.2-2 Server Configuration Tool login window
4.3. Debug log configuration

(1) Displaying the window for debug log configuration
When you log in to Server Configuration Tool, the Server Configuration window
appears.
In the Server Configuration window, press the Shift + Ctrl + F9 key to display the
Debug Log tab. When the Debug Log tab is displayed, select it.
Figure 4.3-1 Window for debug log configuration (before configuration change)
6
(2) Debug log configuration
To collect debug log data, perform the following:
(a) Select the Log Debugging Data check box.
Figure 4.3-2 Window for debug log configuration (after configuration change)
(3) Saving debug log configuration information

Click the Apply button to save the debug log configuration information.
4.4. Terminating Server Configuration Tool

In the Server Configuration window, click the OK button to terminate Server
Configuration Tool.
4.5. Specifying output settings for detailed XML trace log data
- In Windows:
Open the Suite-installation-directory\TuningManager
\jp1pc\agtw\agent\instance-name\jpcagt.ini file using a text editor.
7
Open the /opt/jp1pc/agtw/agent/instance-name/jpcagt.ini file using an editor.
Figure 4.5-1 jpcagt.ini file (for Windows, before setting changes)
(2) Changing the values of properties related to XML trace log

In the [Agent] section, change the property values as follows:
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2
8
Figure 4.5-2 jpcagt.ini file (for Windows, after setting changes)

4.6. Stopping and restarting SMI Agent for EOS

(1) Stopping SMI Agent for EOS
- In Windows:
SMI_Agent_for_EOS_products_2.7, and then Stop Service to stop SMI Agent for EOS.
Stop SMI Agent for EOS by executing the following command:
SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin/stop_server.sh
(2) Restarting SMI Agent for EOS

- In Windows:
9
SMI_Agent_for_EOS_products_2.7, and then Start Service to start SMI Agent for
EOS.
Start SMI Agent for EOS by executing the following command:
SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin/start_server.sh

to start Command Prompt. Execute the jpcstart command to start the instance.
- In Windows:
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
data, and detailed XML trace log data.
5.1. Replicating the failure

Replicate the failure.

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.
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
cd SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin
statusexporter.sh
When the tool ends normally, the following message appears:
StatusExporter end....
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
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 Windows:
(For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.)
Figure 5.4-1 Display when maintenance information collection starts
Verify that the following message is output. If it is output, collection has successfully
ended.
12
Figure 5.4-2 Display when maintenance information collection has successfully ended

When collection of audit log data, debug log data, and detailed XML trace log data is
complete, perform the following procedure to restore the original configuration.
6.1. Restoring debug log configuration

Perform the procedure described in 4.2. Starting Server Configuration Tool to start
Server Configuration Tool.
(2) Displaying the window for debug log configuration

In the Server Configuration window, press the Shift + Ctrl + F9 key to display the
Debug Log tab. When the Debug Log tab is displayed, select it.
13
Figure 6.1-1 Window for debug log configuration (before configuration restoration)
(3) Restoring the debug log configuration

To restore the debug log configuration, perform the following:
(a) Clear the Log Debugging Data check box.
14
Figure 6.1-2 Window for debug log configuration (after configuration restoration)
(4) Saving the debug log configuration information

Click the Apply button to save the debug log configuration information.
(5) Terminating Server Configuration Tool

Click the OK button to terminate Server Configuration Tool.
6.2. Restoring the detailed XML trace log configuration

Open the jpcagt.ini file using a text editor.
- In Windows:
15
Change the [Agent] section as follows:
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1


The next step is to delete the detailed XML trace log data.
Delete the following file:

- In Windows:
File to be deleted:
(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.

to start Command Prompt. Execute the jpcstart command to restart the instance.
16
- In Windows:
-End of document-
17
Collecting XML trace logs when monitoring Cisco switches by
connecting to Cisco Seed switches
1. 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.

failures
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.
space on the drive on which HTnM is installed, because the amount of detailed XML
1
degrade.
as described in 6. Restoring the environment.
4. Procedure for collecting detailed XML trace log data

- In Windows:
2
4.1. Stopping an instance of Agent for SAN Switch
(1) Start Command Prompt.
- In Windows:
From the Start menu, choose Programs, and then Accessories. Click Command
Prompt to start Command Prompt. (The following figure is an example for Windows
2000 Advanced Server.)
When Command Prompt starts, the following window appears:
3
Start the console.
(2) Stop the instance of Agent for SAN Switch.

To stop the applicable instance, execute the following command:
- In Windows:
Even if the above command terminated normally, execute the following command to
confirm that the instance stopped (the status is "Inactive"):
- In Windows:
4
- In Windows:
5
as follows:
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2

6
4.3. Starting the applicable instance of Agent for SAN Switch
Start Command Prompt as described in 4.1. Stopping an instance of Agent for SAN
Switch. Next, execute the jpcstart command as follows to start the instance:
- In Windows:
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:
Name of output files:
CIMClientXML_Trace [?].txt
7
Figure 4.3-1 Output XML trace log data in Windows
8
5. Collecting information by executing the jpcras command
This chapter describes how to collect information by executing the jpcras command.
5.1. Stopping all instances of Agent for SAN Switch

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
/opt/jp1pc/tools/jpcstop agtw
confirm that the instances stopped (the status is "Inactive"):
- In Windows:
9
5.2. Collecting information by executing jpcras command
- In Windows:
documentation.
10
11
6. Restoring the environment
After the collection of detailed XML trace log data finishes, perform the following
procedure to restore the original settings.

If the instance of Agent for SAN Switch has not stopped, stop it as described in 4.1.
Stopping an instance of Agent for SAN Switch.

- In Windows:
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1

12

- In Windows:
[?] is a numeric value from 0 to 63.
6.4. Starting an instance of Agent for SAN Switch

To start the instance of Agent for SAN Switch, perform the procedure described in 4.3.
Starting the applicable instance of Agent for SAN Switch.
-End of document-
13
(3.5) For CISCO (DCNM-SAN SMI-S Agent) (7.2.1 or later)
You can acquire DCNM-SAN support information from the DCNM-SAN window in the GUI.
(A) From the DCNM-SAN window, select Tools, Health, and then Show Tech Support. In the
window that opens, acquire DCNM-SAN support information.
(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.4 EAP Agent

For EAP Agent, in addition to the data acquired using the RAS information collection command
described in 4.1.5, you need to acquire the monitored resources information manually. For details
about acquiring monitored resources information manually, refer to the section "Data collection
procedure" in "Handling errors and troubleshooting" of the following manual:
- In Ver.6
- In Ver.7
- In Ver.8
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. The required time for executing the RAS command

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 Performance Specification
Server identification Server A Server B
Installed Products Tuning Manager server version Agent for RAID Version 6.0.0
6.0.0
Device Manager version 6.0.0

Collecting XML trace and DCNM-SAN support information when
using DCNM SAN SMI-S Agent to monitor Cisco switches
1. 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.

failures
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.
space on the drive on which HTnM is installed, because the amount of detailed XML
1
degrade.
as described in 6. Restoring the environment.
4. Procedure for collecting detailed XML trace log data

- In Windows:
2
(1) Start Command Prompt.
- In Windows:
From the Start menu, choose Programs, and then Accessories. Click Command
Prompt to start Command Prompt. (The following figure is an example for Windows
2000 Advanced Server.)
When Command Prompt starts, the following window appears:
3
Start the console.
(2) Stop the instance of Agent for SAN Switch.

To stop the applicable instance, execute the following command:
- In Windows:
confirm that the instance stopped (the status is "Inactive"):
- In Windows:
4
4.2. supportsave data configuration
If a failure occurs in a switch monitored by an instance of Cisco DCNM-SAN SMI-S Agent, you
need to acquire DCNM-SAN support information.
The procedure for acquiring support information in DCNM-SAN 5.2 is as follows.
If you have a DCFM license:

(1) From the DCNM-SAN window, select Tools, Health, and then Show Tech Support.
(2) In the Show Tech Support window that opens, select the check boxes of the switches you want to
collect support information for.
(3) For Save Map In File, select the JPEG check box.
(4) Select the Compress all files as check box, and then select the folder to which the output of the
show tech-support command is to be stored. (The output is compressed in zip format.)
(5) Confirm that the Command text box shows the default setting (show tech-support
5
details), and then click the Run button.
6
- In Windows:
7
as follows:
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2

8
4.4. Starting the applicable instance of Agent for SAN Switch
Switch. Next, execute the jpcstart command as follows to start the instance:
- In Windows:
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:
Name of output files:
CIMClientXML_Trace [?].txt
9
Figure 4.3-1 Output XML trace log data in Windows
10
5. Collecting information by executing the jpcras command
This chapter describes how to collect information by executing the jpcras command.
5.1. Stopping all instances of Agent for SAN Switch

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
/opt/jp1pc/tools/jpcstop agtw
confirm that the instances stopped (the status is "Inactive"):
- In Windows:
11
5.2. Collecting information by executing jpcras command
- In Windows:
documentation.
12
13
6. Restoring the environment
After the collection of detailed XML trace log data finishes, perform the following
procedure to restore the original settings.

If the instance of Agent for SAN Switch has not stopped, stop it as described in 4.1.
Stopping an instance of Agent for SAN Switch.

- In Windows:
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1

14

- In Windows:
[?] is a numeric value from 0 to 63.
6.4. Starting an instance of Agent for SAN Switch

To start the instance of Agent for SAN Switch, perform the procedure described in 4.3.
Starting the applicable instance of Agent for SAN Switch.
-End of document-
15
OS Windows Server 2003 Enterprise Windows Server 2003 R2
Edition Enterprise Edition
CPU Intel Core 2 Duo E6850 (3.0 GHz) Intel Core 2 Duo E6850 (3.0
GHz)
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 Logical device 61,739
Storage Platform V
LUSE 1,270
VDEV 57,355
Array group 96
Port 96
CLPR 2
Pool 12
Table 4.3-3: The result of the required time for getting RAS information
Command The required time (Second)
hcmdsgetlogs 952
htm-getlogs 243
htm-dump 14
jpcprras 66
jpcras (Server A) 24
jpcras (Server B) 30
4.4 Properties of internal logs

Some internal logs allow the user to change the number and size of log files by using properties files.
If new logs overwrite old logs when errors occur, and event messages cannot be identified, increase
the number or size of log files.
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

In Linux:
<Hitachi-Tuning-Manager-installation-directory>/system/sysconf/system.logging.properties
Table 4.4-1 Properties in the system.logging.properties file

Key Description
trace.fileN The maximum allowable number of Main Console trace log files. Specify an
um integer from 1 to 16. The default value is 10.
trace.fileS The file size of Main Console trace logs (in MB). Specify an integer from 1 to
ize 2,048. The default value is 5.
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 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 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.
The following are examples of property specifications:

trace.fileNum=16
trace.fileSize=30

3) Restart the Hitachi Command Suite Tuning Manager service.
In Windows:
<Common-Component-installation-folder>\bin\hcmdssrv /start /server TuningManager
In Solaris:
/opt/HiCommand/Base/bin/hcmdssrv -start -server TuningManager
In Linux:
<Common-Component-Installation-directory>/bin/hcmdssrv -start -server TuningManager
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
Note: To perform an installation in overwrite or update mode, back up the

sdblogger.properties file before installation, and then restore the file back in place
after installation. Executing an installation overwrites the file by using its initial settings.
Table 4.4-2 Properties in the sdblogger.properties file

Key Description
db.log.trace.file The maximum allowable number of Hybrid Store trace log files.
.number Specify an integer from 1 to 16. The default value is 10.
db.log.trace.file. The file size of Hybrid Store trace logs (in MB). Specify an integer
size from 1 to 2,048. The default value is 20.
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.

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.
The following are examples of property specifications:

db.log.trace.file.number=16
db.log.trace.file.size=30
db.log.trace.output.level=30
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.
4.5.1 The background
In the case of collecting RAS information by the hcmdsgetlogs command or htm-getlogs
command in an environment where Tuning Manager server and Agent are installed on

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 .
- A long time is needed to collect RAS information
- The RAS information cannot be sent to Software division or it takes long time to send the RAS
information.
4.5.2 Overview of the contingency plan

In the case where Tuning Manager server and Agent are installed on a same host, the
acquisition of RAS information is divided into two steps. By acquiring RAS information
except Agent Store database in STEP1-1, the log analysis can be begun promptly.
- 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 HDS Software
Send the result of the GSC Division
RAS Info. by the hcmdsgetlogs

hcmdsgetlogs command for initial
command log analysis.
RAS Info. by
the jpcras STEP1-2 STEP2
command Keep the result of Send the result of
the jpcras command the jpcras command
in HDS if Software division
require the result.
Figure 4.5-1: The flow of acquiring RAS information

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.
4.5.4 Details of the contingency plan

The commands to be executed for collecting RAS information are different by a
combination of Tuning Manager server and Agent installed on a host(see Table 4.5-2).

Table 4.5-2: Relationships between installed software and commands for collecting RAS
info.
Tuning Manager Agent only Tuning Manager Server +
Server only Agent
Conventional way hcmdsgetlogs jpcras with hcmdsgetlogs
option all all
Contingency plan (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.
# Environment variable name Value to set

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

Table 4.5-3: The value of environment variable HTM_NOCOLLECT_AGTSTORE
and behavior of the hcmdsgetlogs command and htm-getlogs command
Value of the Is Store Result of the jpcras command Explanations for the contents
environment database
variable excluded in
RAS Info?
1 Y 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
(c)User/report definition.
(otherwise) N specified-directory*/ClMgr/ (1)Log info.
(2)OS info.
(3)Product info.
(4)Database info. on
(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

In Unix (Solaris sh environment):
# HTM_NOCOLLECT_AGNTSTORE=1; export HTM_COLLECT_AGTSTORE
# /opt/HiCommand/Base/bin/hcmdsgetlogs -dir /export/Logs
(STEP1-2)
Execute the jpcras command with option all all to collect Agent Store Database,
and HDS has to keep the result.
Examples: 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 (Solaris):
# ./jpcras /export/Logs all all
- STEP2
If Software division require the result of the STEP2, send the result to Software division.

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) Stop Tuning Manager server.

Execute the following command:
[ In Ver.7.3.0 to earlier than 8.0.0 ]
For Windows:
<Hitachi-Command-Suite-CommonComponent-installation-folder>\bin\hcmdssrv /stop
/server TuningManager
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
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmds64srv stop
(2) Configure the user property file.

The user property file is stored in the following location:
For Windows:
<Tuning-Manager-server-installation-folder>\conf\user.properties
For Solaris:
/opt/HiCommand/TuningManager/conf/user.properties

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
(3) Start Tuning Manager server.

[ In Ver.7.3.0 to earlier than 8.0.0 ]
For Windows:
<Hitachi-Command-Suite-Common-Component-installation-folder>\bin\hcmdssrv /start
For Solaris:
/opt/HiCommand/Base/bin/hcmdssrv -start -server TuningManager
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmdssrv start
[ In Ver.8.0.0 or later ]
For Windows:
<Hitachi-Command-Suite-Common-Component-installation-folder>\bin\hcmds64srv /start
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmds64srv start
(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.
(5) Confirm that the XML file is output.

Confirm that the dump file exists in the following folder or directory:
For Windows:
<Tuning-Manager-server-installation-folder>\logs
For Solaris:
/opt/HiCommand/TuningManager/logs
For Linux:
<Tuning-Manager-server-installation-directory>/logs
The dump file format is as follows:

Chart_<hexadecimal-value>_<integer-value>.xml

(6) Confirm that the message log is output.
Confirm that the KATN12675-I message is output to htmMessage<integer value>.log.
(7) Execute the hcmdsgetlogs command.

Execute the hcmdsgetlogs command. For details about how to use this command, see the
Hitachi Command Suite Tuning Manager Software Server Administration Guide.
(8) Stop Tuning Manager server.

Perform the procedure described in step (1).
(9) Delete the dump file that contains the chart information.
Delete the dump file you checked in step (5).
(10) Disable the user property file settings.

Delete the dumpChartXML property you added in step (2).
(11) Start Tuning Manager server.

Perform the procedure described in step (3).

5. Architecture
5.1 Process composition
(1) In Ver.6.0.0 to earlier than 8.0.0
Host
Process
Tuning Manager Serve r Communication
Collection Manager
Web Container (HBase)
Action Handler
Device Manager
HTTP/HTTPS HTM Agent
HTTP/HTTPS Action Handler
Trap Generator
Web Container (HBase)
Single Sign On service Agent Collector Get data from

Hitachi Web Server( HBase)
Name Server monitored

resource
Web Container (HBase) Agent Store
Correlator
Tuning Service
PFM NS API
HTTP/HTTPS
Master Manager
Web Container (HBase) HTM Agent
Tuning Manager MC Master Store Action Handler
HSSO LIB JDBC PFM NS API
Get data from
View Server Agent Collector monitored
HiRDB
resource
RMI
Agent Store
Web Container (HBase) 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)

# Service Name of process Explanation
1 Hitachi Storage Command This service provides common function of Hitachi Storage
Suite Common Web Service Command Suite, such as consolidated Log in (SSO),
consolidated DB(HiRDB), Common Web Service.,
2 Hitachi Storage Command This service provides the consolidated Log in function (SSO)
Suite Single Sign On Service of Hitachi Storage Command Suite
3 Hitachi Storage Command This service provides the interface for getting data from Agent
Suite TuningService by using CIM-SOAP API. This API is used by HiCommand
Tiered Storage Manager, or getting data from Tuning Manager
server in version 5.0 or later.
This is not supported by Tuning Manager for Linux version
7.1 or later.
4 Hitachi Storage Command This service is the main service of Tuning Manager server.

Suite TuningManager This service provides the function of getting historical data
from Agent, do aggregation for resource axis (device
server) or time axis (hourly daily).
5 Inter Base/Inter Client Inter Base is used by HTnM and HDvM in version 3.5 or
earlier. Manage the DB of Tuning Manager server.
6 Performance Reporter This service provides the function of showing the report of
Agent data, creating the report.
7 PFM - Name Server This service manages the node information of each service of
Collection Manager and Agents. The Communication between
each service of Collection Manager/Agents is based on the
node information managed by Name Server.
8 PFM - Master Manager This service is the main server of Collection Manager,
managing the defined information, providing defined
information to other service of Collection Manager/Agents.
9 PFM - Master Store This service manages the alarm event information.
10 PFM - Correlator This service controls the issue of event between services of
Collection Manager/Agents.
11 PFM - View Server This service is the proxy of the communication between
Collection Manager and the client (Performance Reporter).
12 PFM - Trap Generator This service issues the SNMP Trap when alarm occurs.
13 PFM - Action Handler This service does action when alarm occurs.
14 Agent Collector This service provides the function of getting data from
monitored resource, evaluating the defined alarm when data is
collected.
15 Agent Store This service manages Agents DB, stores the data got by Agent
Collector.
16 PFM - Status Server Service status manager
[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.

(2) Ver.8.0.0 to earlier than Ver.8.1.3
Figure 5.1-2 Process composition of HTM (Ver.8.0.0 to earlier than Ver.8.1.3)
Table 5.1-2 Explanation of process (Ver.8.0.0 to earlier than Ver.8.1.3)

1. Tuning Manager REST Service This service receives requests from Tuning Manager API, and
then returns the performance information obtained from Agent
REST Service to Tuning Manager API Client.
2. Agent REST Service This service receives requests from Tuning Manager REST
Service, reads the performance information file output by
Agent Collector, and then returns the information to Tuning
Manager REST Service.
3. HBase 64 Storage Mgmt Web This service provides common function of Hitachi Storage
Service Command Suite, such as consolidated Log in (SSO),
4. HBase 64 Storage Mgmt SSO This service provides the consolidated Log in function (SSO)
Service of Hitachi Storage Command Suite
5. Hitachi Command Suite This service is the main service of Tuning Manager server.
TuningManager This service provides the function of getting historical data

6. Performance Reporter This service provides the function of showing the report of
7. PFM - Name Server This service manages the node information of each service of
8. PFM - Master Manager This service is the main server of Collection Manager,
9. PFM - Master Store This service manages the alarm event information.
10. PFM - Correlator This service controls the issue of event between services of
11. PFM - View Server This service is the proxy of the communication between
12. PFM - Trap Generator This service issues the SNMP Trap when alarm occurs.
13. PFM - Action Handler This service does action when alarm occurs.
14. Agent Collector This service provides the function of getting data from
collected. When Tuning Manager API is enabled, this service
outputs data to the operation performance information file.
15. Agent Store This service manages Agents DB, stores the data got by Agent
Collector.
16. PFM - Status Server Service status manager

(3) Ver.8.1.3 to earlier than Ver.8.2.1
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)
1 Tuning Manager REST Service This service receives requests from Tuning Manager API, and
2 Agent REST Service If the data storage format is Store database, when this
service receives a request from Tuning Manager REST
Service, it reads the performance information file that was
output by Agent Collector and returns the file to Tuning
If the data storage format is Hybrid Store, this service
manages Agents DB and returns the data as required.
3 HBase 64 Storage Mgmt Web This service provides common function of Hitachi Storage
4 HBase 64 Storage Mgmt SSO This service provides the consolidated Log in function (SSO)

5 Hitachi Command Suite This service is the main service of Tuning Manager server.
6 Performance Reporter This service provides the function of showing the report of
7 PFM - Name Server This service manages the node information of each service of
8 PFM - Master Manager This service is the main server of Collection Manager,
9 PFM - Master Store This service manages the alarm event information.
10 PFM - Correlator This service controls the issue of event between services of
11 PFM - View Server This service is the proxy of the communication between
12 PFM - Trap Generator This service issues the SNMP Trap when alarm occurs.
13 PFM - Action Handler This service does action when alarm occurs.
14 Agent Collector This service provides the function of getting data from
collected. If Tuning Manager API is enabled, this service
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 PFM - Status Server Service status manager

(4) Ver.8.2.1 or later
Figure 5.1-3 Process composition of HTM (Version 8.2.1 or later)
Table 5.1-3 Explanation of process (Version 8.2.1 or later)

1. Tuning Manager REST Service This service receives requests from Tuning Manager API, and
2. Agent REST Service If the data storage format is Store database, when this
service receives a request from Tuning Manager REST
Service, it reads the performance information file that was
output by Agent Collector and returns the file to Tuning
If the data storage format is Hybrid Store, this service
manages Agents DB and returns the data as required.
In version 8.2.1 or later, alert definitions of each agent are
managed and used for threshold evaluation of performance
information to issue alerts.
3. HBase 64 Storage Mgmt Web This service provides common function of Hitachi Storage
4. HBase 64 Storage Mgmt SSO This service provides the consolidated Log in function (SSO)
5. Hitachi Command Suite This service is the main service of Tuning Manager server.

6. Performance Reporter This service provides the function of showing the report of
7. PFM - Name Server This service manages the node information of each service of
8. PFM - Master Manager This service is the main server of Collection Manager,
9. PFM - Master Store This service manages the alarm event information.
10. PFM - Correlator This service controls the issue of event between services of
11. PFM - View Server This service is the proxy of the communication between
12. PFM - Trap Generator This service issues the SNMP Trap when alarm occurs.
13. PFM - Action Handler This service does action when alarm occurs.
14. Agent Collector This service provides the function of getting data from
collected. If Tuning Manager API is enabled, this service
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. PFM - Status Server Service status manager

5.2 Communication Sequence
5.2.1 Sequence for starting up the service of Collection Manager/Agents
Name Server Master Manager
?-NR Get the Service ID

information
Register the service

Master Manager
information Master Store started
Get the node ?-NI

information of
Master Manager
Get the product ?-PIT

information
Update the service

information
Register the
service id
information
Register the Store.

View Server Master Store started
Get the node ?-NI

information of
Master Manager

information

id information
Register the client

information R-PIT
Get the Agent ?-AD

information ?-AD
Get the dictionary ?-DIC

information R-DIC View Server started

Name Server Master Manager Correlator
Get the node ?-NI

information of
Master Manager
Get the Agent ?-EAR

information

information A-NI
Register the Service

ID information
Get the event ?-EER

information R-EER Action Handler Correlator started
Get the node ?-NI

information of
Master Manager

information

ID information

information R-PIT
Register the Action

Handler
Get the Action ?-ACT

information R-ACT
Register the
event information
Register the event

information Action
Small:Handler
6GB started
Medium: 6GB

Name Server Master Manager Correlator Trap Generator
Get the node ?-NI

information of
Master Manager

information

ID information
Register the event

information
Register the event

information
Trap Generator started
Agent Store
Get the node ?-NI

information of
Master Manager

information enough

information

ID information
space check)
Make sure that there is
Register the Store

F (Disk
information
Agent Store started

Name Server Master Manager Agent Store Agent Collector
Get the node ?-NI

information of
Master Manager
Get the node ?-NI

information of Agent
Store

information

ID information
Register the Agent

E-AR
information
Correlator
Update the Agent

information
Get the dictionary ?-DIC

information
Get the alert ?-ALM #8 Check

information

information
Receive the event of

alert Agent Collector started

5.2.1 Sequence for starting up the service of Tuning Manager server
Core initialization thread

UI layer initialization thread Common-part initialization
thread This step includes the following:
- Initializing the log output
- Reading each property file
[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
Startup request 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
Begin startup process syslog/ event log.
[Cause of the Error]

A property contains an invalid value in the property file
Initialize common part
shown in the message.
Create core initialization

Start
thread
Initialize UI layer Initialize the core

common part
(see Figure 5.2.2-2)
Create initialization thread

Start for HTnM UI layer End
End
No Has the
core been
initialized?
Yes
Initialize HTnM UI layer
End of startup processing
Figure 5.2.2-1 Overview of the startup sequence for the Tuning Manager server

Start the initialization
[Error Example]
of the core
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 [Cause of the Error]
Check any logs that contain information on the component
shown in the KATN10011-E message, and then determine the
cause of the startup failure.
Attempt to start up [Startup Retry Interval]
Performance Reporter
If a startup check fails, up to 19 retries are made, once every 30
seconds (default).
Make sure that Collection
Manager is running
Make sure that Performance

Reporter is running
Make sure that the connection to the HTnM

database has been established
[Error Example]
Is the database schema If a connection to HDvM cannot be established, the
version up-to-date? KATN15014-E message is output to log files
(htmMessage.log/htmTrace.log) and the login window.
[Cause of the Error]

Initialize hibernate 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
Make sure that a connection to HDvM that is trying to be connected to.
HDvM has been established - 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
Initialize various seconds (default).
features
Start up the scheduler
End
Figure 5.2.2-2 Core initialization sequence

6. How to Start or Stop Services
6.1. Tuning Manager server services
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:
- HiRDB/EmbeddedEdition _HD0
- 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

In Windows, services can be started or stopped from SCM.
For details on how to use commands to start or stop services, see the manual.
(1) Starting services from SCM

You can start the Agent Store service and the Agent Collector service from SCM.
The Agent Store service can be started independently. The Agent Collector service cannot be
started independently, because it is dependent on the Agent Store service. When the Agent Store
service starts, the Agent Collector service also starts automatically.

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
Figure 6.4-1: RAID Agent services with the instance name of

9970v started or stopped with the Services window
(2) Stopping services from SCM

In addition to starting these services from SCM, you can also stop the Agent Store service and the
Agent Collector service from SCM.
The Agent Store service can be stopped independently. The Agent Collector service cannot be
stopped independently, because it is dependent on the Agent Store service. When the Agent Store
service stops, the Agent Collector service also stops automatically.
The following shows an example of stopping the RAID Agent services whose instance name is
9970v.
(A) Open the Services window.
(B) Stop the following services:
- PFM-Agent Store for RAID 9970v
- PFM-Agent for RAID 9970v

7. Other Information
7.1. Disabling IPv6 (Ver. 6 or later)
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.
(1) Disabling IPv6

Execute the jpcnsconfig IPv6 command with disable specified. The following shows examples of
executing the command:
In Windows
Suite-installation-directory\TuningManager\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)
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)
(2) Confirming that IPv6 is disabled

Execute the jpcnsconfig ipv6 command with display specified. The command displays disable if
IPv6 is disabled, or available if IPv6 is enabled. The following shows examples of executing the
command:
In Windows
Suite-installation-directory\TuningManager\jp1pc\tools\ jpcnsconfig ipv6 display
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
/opt/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)
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. Notice for linkage with Tiered Storage Manager

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

after executing the following operations.
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
- 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. Notes on the hcmdsdbclustersetup command
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.
(1) Use the following command to stop all services.

hcmdssrv /stop
hcmds64srv /stop
(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.
(3) Edit the HiRDB definition file as follows:

Name of the file to be edited: D:\HiCommand\Base\HDB\CONF\pdsys
Name of the file to be edited: D:\HiCommand\Base64\HDB\CONF\pdsys
After the modification:

set pd_max_users = 5

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.
(4) In the Windows services panel, restart the following service.

HiRDB/EmbeddedEdition _HD0
(5) Use the following command to start the HiRDB service.

hcmdsdbsrv /start
hcmds64dbsrv /start
(6) Use the following command to confirm that the HiRDB service has started.
hcmdsdbsrv /status
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.
hcmdsdbclustersetup /createcluster /databasepath I:\share\HiCommand\HiRDB /exportpath
D:\HiCommand\work /auto
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

(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
(1) Stop HTnM and HDvM.

(2) Upgrade HDvM to 6.2.0 or after.
(3) Start HDvM and Tuning Manager server
(4) Perform the following operations that remove the SMS where Auto Migration was done from
monitoring target.
a) Click the [Resource] button and the [Subsystem] button on the Explorer area of HDvM.
b) Select the SMS instance on the resource tree.
c) Click the [Remove Subsystem] button.
(5) Perform the following operations that add the SMS where Auto Migration was done as a
monitoring target.
a) Click the [Resource] button and the [Subsystem] button on the Explorer area of HDvM.
b) Select the subsystem node on the resource tree.
c) Click the [Add subsystem] button.
< 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

Manager, as described in the Deleting Service Information section of the following manual:
[ manual ]
- In Ver.6
- In Ver.7
- In Ver.8
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".

- 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.
- All the service information for the Agent on the "C44A1DE6A63543D" host are deleted from the
database managed by Collection Manager.
In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl 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.

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

7.7 Store database error detection tool (HTnM 6.4 or later)
7.7.1 Overview of the Store database error detection tool
7.7.1.1 Background and objective

An error occurred where data in a Store database becomes corrupted when the
data model is upgraded. For details, see SD-EN-HTNM-209.
The Store database error detection tool can be used to check whether data in a
Store database has been corrupted. The tool can also predict whether data is likely
to become corrupted in the future.
What this tool can detect:

Whether data in a Store database has become corrupted, and the extent of the
corrupted data
Whether data will become corrupted when the data model of a Store database
is upgraded
7.7.1.2 Conditions under which data in a Store database becomes corrupted
This problem may occur when both of the following conditions (1), (2), and (3) are
met:
Note that the Store database error detection tool determines whether data has
been corrupted by using conditions (1) and (2) below.
Conditions under which data corruption in a Store database is checked:

(1) The data storage method of the Store database is Store version 2.0
(2) Data is collected in a multi-instance environment, and during one data
collection period, data is divided into multiple blocks (the maximum size of
each block being 64 KB).
(3) Either of the following operations is performed:
(a) Perform an upgrade installation that changes the data model version.
(b) The "jpcdbctrl dmconvert" command is used to change the data model
version of backup data.
<Components affected>
Software
HTnM server
HTnM - Agent for RAID

HTnM - Agent for Server System
HTnM - Agent for Oracle
[Combination of version where Store database data corrupt]

The following tables show the combinations of Agent versions for which this
problem occurs.
<Combinations of Agent versions for which this problem occurs (HTnM - Agent for
RAID)>
Product version Upgraded to:
6.2.0
6.0.0
6.1.0
6.3.0
6.4.0 or later
6.2.0-00
6.2.0-01
6.2.0-02
6.0.0 X X X O O O
Upgraded from:
Product version
6.1.0 X X O O O
6.2.0 6.2.0-00 X O O O
6.2.0-01 O O O
6.2.0-02 O O
6.3.0 O
[Legend] O:No problem occurs X:A problem occurs

<Combinations of Agent versions for which this problem occurs(HTnM - Agent for
Server System)>
6.2.0
6.0.0
6.1.0
6.3.0
6.4.0 or later
6.2.0-00
6.2.0-01
6.2.0-02
6.0.0 O O O O O O
Product version
Upgraded from:
6.1.0 O O O O O
6.2.0 6.2.0-00 O O O O
6.2.0-01 O O O
6.2.0-02 O O
6.3.0 O
<Combinations of Agent versions for which this problem occurs(HTnM - Agent for
Oracle)>
6.2.0
6.0.0
6.1.0
6.3.0
6.4.0 or later
6.2.0-00
6.2.0-01
6.2.0-02
6.0.0 O O O O O O
Upgraded from:
Product version
6.1.0 O O O O O
6.2.0 6.2.0-00 O O O O
6.2.0-01 O O O
6.2.0-02 O O
6.3.0 O

7.7.1.3 When to use the Store database error detection tool
For the following cases, use the Store database error detection tool to check if
data has become corrupted. Also use the tool to determine whether data will become
corrupted when an upgrade installation is performed:
When a Store database is upgraded to a version that is known to have this
problem#1
When you are planning on upgrading a Store database to a version that is
known to have this problem#1
When you suspect that data has become corrupted
#1: For details on the versions in which data in the Store database becomes
corrupted, see 7.7.1.2.
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 Required disk space
The directories that contain When the Store service of the target Agent is running:
the Store databases that will Disk space equal to the data file size of the Store
be checked database#1
When the Store service of the target Agent is not running:

None
In 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.

#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 member of the Administrators group
UNIX root user
7.7.2 How to use the Store database error detection tool
7.7.2.1 Procedure
Please execute the Store database error detection tool with following Step.
[Step1] Change the current directory.
[Step2] Run the Store database error detection tool.
[Step3] Check the results, and then take an appropriate action.
Details of each Step are shown as follows.
- Step 1: Change the current directory.

From the console#1, change the current directory to the CD-ROM or DVD-ROM#2 directory
where the Store database error detection tool is located, and then run the tool.
#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
1 Windows 2003 <CD-ROM drive>\
Server
Windows_2K3_2K8\Maintenance_Tool\Windows_2K3
2 Windows 2008 <CD-ROM drive>\
\Windows_2K3_2K8\Maintenance_Tool\Windows_2K8
3 Solaris <CD-ROM drive>/Solaris/Maintenace_Tool
4 Windows 2003 <CD-ROM drive>\Windows_2K3\Maintenance_Tool
Agen
5 Windows 2003 <CD-ROM drive>\Windows-IPF_2K3\Maintenance_Tool

(IPF)
6 Windows 2008 <CD-ROM drive>\Windows_2K8\Maintenance_Tool
7 Windows 2008 <CD-ROM drive>\Windows-IPF_2K8\Maintenance_Tool
(IPF)
8 Solaris <CD-ROM drive>/Solaris/Maintenace_Tool
9 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
pe
1 Windows 2003 none(*)
Server
2 Windows 2008 none(*)

3 Solaris none(*)
4 Windows 2003 <DVD-ROM
Agent
drive>\AGENTS\HTNM\Windows_2K3\Maintenance_Tool
5 Windows 2008 <DVD-ROM
drive>\AGENTS\HTNM\Windows_2K8\Maintenance_Tool
6 Solaris <DVD-ROM
drive>\AGENTS\HTNM\Solaris\Maintenance_Tool
7 Solaris(x64) <DVD-ROM
drive>\AGENTS\HTNM\Solaris-x64\Maintenance_Tool
8 AIX <DVD-ROM drive>\AGENTS\HTNM\AIX\Maintenance_Tool
9 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.
- Step 2: Run the Store database error detection tool.

Execute the command below to run the Store database error detection tool. Note
that you should redirect the standard output and standard error output file on a
local disk when executing this command.
# Command
1 fix12753 check all > file-name 2>&1
Note: For a database connected to a Store service running on a logical host in a

cluster environment, run the Store database error detection tool on the
executing node.
- Step 3: Check the results, and then take an appropriate action.

View the local disk files that contain the output results of the Store database
error detection tool. In addition to these files, lists of data pertaining to the errors
that have been detected will be output to these files. For details on the output files,
see 7.7.6.1.
(1) Cases in which the Store database error detection tool was successfully
executed:
(a) When no errors were found in a Store database
If no messages that begin with [Error] or [Warning] are output to the output
files, no error have occurred in a Store database. Therefore, no action is
required.
(b) When corrupted data was found

If data has become corrupted, the following message is output to the output
files:
[Error] At least one piece of data before date-and-time has been
corrupted. (record = record-ID[, drawer = summarization-unit])
See 7.7.3.1 to take appropriate action.
(c) When it is predicted that data will become corrupt in the future
If there is the possibility that data will become corrupted in the future, the
following message is output to the output files:
[Warning] If the data model version is upgraded, at least one piece
of 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

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

error detection tool:
- Change the virus-checking application settings so that the file system
directories that contain the Store database data you want to check are
not monitored.
- Change the virus-checking application settings so that any files in the
file system with the extensions DB or IDX are not monitored.
7.7.2.3 Execution examples

This section contains execution examples for Windows 2003 and Solaris 10.
(1) Windows 2003

(a) Log in
Log in as a user who belongs to the Administrators group of the local computer.
(b) Insert the CD-ROM or DVD-ROM

Insert the installation CD-ROM or DVD-ROM
(c) Move the current directory

<In Ver.6.4>
Move the current directory to the following directory.
# Command line
1 cd <CD-ROM drive>\Windows_2K3_2K8\Maintenance_Tool\Windows_2K3
<In Ver.7.0 to earlier than 8.0>
# Command line
1 cd <DVD-ROM drive>\ AGENTS\HTNM\Windows_2K3\Maintenance_Tool
(d) Execute the Store database error detection tool

After confirming a Store service is stopped, execute fix12753 check all.
# Command line
1 fix12753 check all > C:\tmp\check_result.txt 2>&1

(e) Checking of execution result
Confirming the content of C:\tmp\check_result.txt.
Output file example
Processing agent. servicekey=agtd, instance=test01
Processing StoreDB. dir=C:\Program

Files\HiCommand\TuningManager\jp1pc\agtd\store\test01
Processed 39112 records for Data type PI
[Error] At least one data before 2008/11/3 is broken (Record= LDS, Drawer= day)
[Error] At least one data before 2008/11/3 is broken (Record= LDS, Drawer= week)
[Error] At least one data before 2008/11/1 is broken (Record= LDS, Drawer= month)
[Error] At least one data before 2008/1/1 is broken (Record= LDS, Drawer= year)
[Error] At least one data before 2008/11/3 is broken (Record= LDS1, Drawer= day)
[Error] At least one data before 2008/11/3 is broken (Record= LDS1, Drawer= week)
[Error] At least one data before 2008/11/1 is broken (Record= LDS1, Drawer= month)
[Error] At least one data before 2008/1/1 is broken (Record= LDS1, Drawer= year)

Files\HiCommand\TuningManager\jp1pc\agtd\store\test02
[Information] No defect data found on this DB. (Store Version=2.0)
Data has been
Processing agent. servicekey=agte corrupted..
Processing StoreDB. dir=C:\Program Files\HiCommand\TuningManager\jp1pc\agte\store

Processing agent. servicekey=agtt
Processing StoreDB. dir=C:\Program Files\HiCommand\TuningManager\jp1pc\agtt\store

Processing agent. servicekey=agtw, instance=test03

Files\HiCommand\TuningManager\jp1pc\agtw\store\test03

Files\HiCommand\TuningManager\jp1pc\agtw\store\test04
Processing agent. servicekey=agt0
Processing StoreDB. dir=C:\Program Files\HiCommand\TuningManager\jp1pc\agt0\store

Process completed.
By viewing these results, you can see that data in the Store database has been
corrupted.

(f) Checking the output file
Open the following file:
# File
1 Suite-installation-directory\TuningManager\jp1pc\tools\log\fix12753_check_error.log{01|02}
The following is an example of information that might be output:

Output file example
Date and Time, ServiceKey, Instance Name, Directory, Record Name, Drawer, Start Date, End Date
2010/04/08 11:34, agtd, test01, C:\Program
Files\HiCommand\TuningManager\jp1pc\agtd\store\test01, LDS, day, 2008/11/3, 2008/12/18
Files\HiCommand\TuningManager\jp1pc\agtd\store\test01, LDS, week, 2008/11/3, 2008/12/15
Files\HiCommand\TuningManager\jp1pc\agtd\store\test01, LDS, month, 2008/11/1, 2008/12/18
Files\HiCommand\TuningManager\jp1pc\agtd\store\test01, LDS, year, 2008/1/1
Files\HiCommand\TuningManager\jp1pc\agtd\store\test01, LDS1, day, 2008/11/3, 2008/12/1
Files\HiCommand\TuningManager\jp1pc\agtd\store\test01, LDS1, week, 2008/11/3, 2008/12/15
Files\HiCommand\TuningManager\jp1pc\agtd\store\test01, LDS1, month, 2008/11/1, 2008/12/1
Files\HiCommand\TuningManager\jp1pc\agtd\store\test01, LDS1, year, 2008/1/1
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
,<In Ver.7.0 to earlier than 8.0>

*)Note that the execution procedure in a Solaris environment that is described in
this section assumes that the DVD-ROM drive is mounted to the /dvdrom/dvdrom0
directory.
# Command line
1 /usr/sbin/mount -F cdfs -r device-special-file-name /dvdrom/dvdrom0
(a) Log in
Log in to the host as the root user. Alternatively, use the su command to switch to
the root user.
(b) Insert the CD-ROM or DVD-ROM

Insert the installation CD-ROM or DVD-ROM.
(c) Move the current directory

<In Ver.6.4>
# Command line
1 cd /cdrom/cdrom0/Solaris/Maintenance_Tool
<In Ver.7.0 or later>

# Command line
1 cd /dvdrom/dvdrom0/AGENTS/HTNM/Solaris/Maintenance_Tool
(d) Execute the Store database trouble detection tool

After confirming a Store service is stopped, execute fix12753 check all.
# Command line
1 ./fix12753 check all > /work/check_result 2>&1
*) "/work" is an arbitrary work directory.

(e) Checking of execution result
Confirming the content of /work/check_result.
Output file example

Processing StoreDB. dir=/opt/jp1pc/agtd/store/test01

[Error] At least one data before 2008/11/3 is broken (Record= LDS, Drawer= day)
[Error] At least one data before 2008/11/3 is broken (Record= LDS, Drawer= week)
[Error] At least one data before 2008/11/1 is broken (Record= LDS, Drawer= month)
[Error] At least one data before 2008/1/1 is broken (Record= LDS, Drawer= year)
[Error] At least one data before 2008/11/3 is broken (Record= LDS1, Drawer= day)
[Error] At least one data before 2008/11/3 is broken (Record= LDS1, Drawer= week)
[Error] At least one data before 2008/11/1 is broken (Record= LDS1, Drawer= month)
[Error] At least one data before 2008/1/1 is broken (Record= LDS1, Drawer= year)
Processing agent. servicekey=agte

Data has been
Processing StoreDB. dir=/opt/jp1pc/agte/store corrupted.
Processing agent. servicekey=agtu
Processing StoreDB. dir=/opt/jp1pc/agtu/store

Processing StoreDB. dir=/opt/jp1pc/agtw/store/test03

Processing StoreDB. dir=/opt/jp1pc/agtw/store/test04

Processing agent. servicekey=agt0
Processing StoreDB. dir=/opt/jp1pc/agt0/store

Process completed.
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}

The following is an example of information that might be output:
Output file example
Date and Time, ServiceKey, Instance Name, Directory, Record Name, Drawer, Start Date, End Date
2010/04/08 11:34, agtd, test01, /opt/jp1pc/agtd/store/test01, LDS, day, 2008/11/3, 2008/12/15
2010/04/08 11:34, agtd, test01, /opt/jp1pc/agtd/store/test01, LDS, week, 2008/12/18
2010/04/08 11:34, agtd, test01, /opt/jp1pc/agtd/store/test01, LDS, month, 2008/11/1,
2008/12/1
2010/04/08 11:35, agtd, test01, /opt/jp1pc/agtd/store/test01, LDS, year, 2008/1/1
2010/04/08 11:35, agtd, test01, /opt/jp1pc/agtd/store/test01, LDS1, day, 2008/12/18
2010/04/08 11:35, agtd, test01, /opt/jp1pc/agtd/store/test01, LDS1, week, 2008/11/3,
2008/12/15
2010/04/08 11:35, agtd, test01, /opt/jp1pc/agtd/store/test01, LDS1, month, 2008/11/1,
2008/12/1
2010/04/08 11:38, agtd, test01, /opt/jp1pc/agtd/store/test01, LDS1, year, 2008/1/1
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.

7.7.3 If an error is found in a Store database
7.7.3.1 If corrupt data is detected in a Store database

Invalid values might be displayed on a report if the data has been corrupted. If
this happens, choose any of the following methods to correct the problem. The first
method is recommended if the corrupted data has no effect on current operations.
1) Continuing operating as usual

In order to avoid confusion, we recommend not using the corrupt data to
create reports.
Other than the displaying of corrupt data, no other problems will occur (for
example, a service fails to properly start). In addition, corrupt data will
automatically be deleted from a Store database when the retention period for the
corresponding record ends.
2) Recovers before updated

When there is a backup of the Store database created before the upgrade
installation of HTnM Agents was performed:
Use the following procedure to restore the Store database:
(1) Uninstall the relevant HTnM Agents.
(2) Perform a new installation of the previous version of HTnM Agents.
(3) Set up HTnM Agents. For a multi-instance Agent, create instances with
the same names that were used before the upgrade installation.
(4) Use the "jpcresto" command to restore the Store database from the
backup.
Note: When this procedure is used, the version of HTnM Agents that was
used before the upgrade installation must be used.
3) Initialization of Store database

When there is no backup of the Store database created before the upgrade
installation of HTnM Agents was performed:
Use the "jpcctrl clear" command to clear the Store database.
Note: When this procedure is used, the upgraded version of HTnM Agents
can be used, but the Store database that was being used before the
upgrade installation cannot be inherited.

7.7.3.2 If data might become corrupted in the future
The data model of a Store database is updated when an Agent is upgraded or
when the jpcdbctrl dmconvert command is executed to backup a Store database.
Obtain HTnM version 6.2.0-02 or later, and then update the data model of the Store
databases after that.
When HTnM server and HTnM Agents are installed on the same host, perform
the upgrade installation of HTnM server to the fixed version first. If the upgrade
installation of HTnM Agents to the fixed version is performed first, this problem
cannot be fixed.
7.7.4 Tool performance

The processing time of the Store database error detection tool varies depending on
system specifications, the size of the data files and the number of instance. The
following tables list estimated processing times.
Table 7.7-4: Benchmark environments
# Platform Windows UNIX
items
1 OS Windows 2003 Solaris 10
2 CPU Core 2 2.13 GHz Sparcv9 1000MHz
3 Memory 1.97GB 2.0GB
4 number of instance 5 5
Table 7.7-5: Estimated processing times (Windows)

# Estimated processing time
1 1 minute per 1 GB of data#1
#1: "Data" refers to the Store database data files that will be checked.
Table 7.7-6:Estimated processing times (Solaris)

# Estimated processing time
1 1 minute per 1 GB of data#1
#1: "Data" refers to the Store database data files that will be checked.

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.
7.7.5.3 If the cause of an error cannot be identified

If the cause of an error cannot be identified, collect the items shown in the
following table, and send them to SD.
Table 7.7-7: Items to collect if the cause of an error cannot be identified

# Item
1 Log information collected by the jpcras all command
For details on the jpcras command, see 4.1.5.
2 Files specified for command execution

7.7.6 Detailed specifications
7.7.6.1 Output files

After executing the Store database error detection tool, lists of data pertaining to
errors that are found are output to files. The following table shows the types of output
data and the file paths.
Table 7.7-8: File paths for the Store database error detection tool output files
# Data type File path
1 List of data that has [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}(*)
2 List of data that [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
# Item Description
1 Date and time Local date and time when the log data was output. The format
is as follows:
yyyy/mm/dd hh:mm:ss
2 Service key The service key. The format is as follows:
agtx
3 Instance name The instance name. This item will be blank if the Agent is a
single instance agent, or the command was executed for a
specific database.
4 Directory Directory of the database that contains the data to be output
5 Record name The record name of data to be output
6 Drawer Interval used for the summarization of output data. The unit is
one of the following: minute, hour, day, week, month, or year.
7 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
8 End date#1, #2 The ending date (in local time) of the time period in which the

data to be output exists. The format is as follows: yyyy/mm/dd
If the ending date is same as the starting date, the ending date
is not output.
#1: If a start date and end date are output, then all of the data between these dates is
corrupt.
#2: The end date is only output when the data in a record is corrupt for 2 or more days
in a row.
The following is an example of an output file:

Example of the output file
DateAndTime, ServiceKey, Instance Name, Directory, Record Name, Drawer, Start Date, End
Date
2010/02/12 00:31, agtz, inst1, C:\Program Files\Hitachi\jp1pc\agtz\store\inst1, MLT, min,
2010/2/10, 2010/2/11
2010/02/12 00:31, agtz, inst1, C:\Program Files\Hitachi\jp1pc\agtz\store\inst1, MLT, hour,
2010/2/4, 2010/2/11
2010/02/12 00:31, agtz, inst1, C:\Program Files\Hitachi\jp1pc\agtz\store\inst1, MLT, day,
2009/10/16, 2010/2/11
2010/02/12 00:31, agtz, inst1, C:\Program Files\Hitachi\jp1pc\agtz\store\inst1, MLT, week,
2009/10/11, 2010/2/7
2010/02/12 00:31, agtz, inst1, C:\Program Files\Hitachi\jp1pc\agtz\store\inst1, MLT,
month, 2009/9/30, 2010/1/31
2010/02/12 00:31, agtz, inst1, C:\Program Files\Hitachi\jp1pc\agtz\store\inst1, MLT, year,
2008/12/31, 2009/12/31

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.
Processing BackupDB dir=directory

Standard output
Error detection for backup files of Store data base will now begin.
Processing ImportDB. dir=directory

Standard output
Error detection for import files of Store data base will now begin.

Processing Partial BackupDB dir=directory
Standard output
Error detection for the partial backups of a Store database will now begin.
Processing DB. dir=directory

Standard output
Error detection for the individual backups of a Store database will now begin.
Process completed.
Standard output
Error detection process was completed.
(S) Processing is ended.
Processd number of records records for Data type database ID

Standard output
number-of-processed-records Store database records have been processed.
[Information] No defect data found on this agent. (Store Version=store version)

Standard output
No corrupt data was found for the Agent.
[Error] At least one data before date is broken. (record=record ID[, drawer=
summarization-unit])
Standard error output
Corrupt data has been found. Processing will continue.
(O) See 7.7.3.1 to take appropriate action.

[Warning] If data model version will be upgraded, then at least one data will be broken.
(record=record ID[, drawer=summarization-unit])
Data that might become corrupted in the future has been found.
(O) See 7.7.3.2 to take appropriate action.
[Error] Backup processing failed. (rc=return code)

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)

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

[Error] DB check processing fails. (rc=return-code)
An attempt to check a Store database has failed.
(S) Stops processing of the Store database. If there are any unprocessed Store
(O) Make sure that the current directory where Store database error detection tool is
executed is the same as the actual directory of the tool. If the directories are different,
change the current directory to the directory the tool is in, and then run the tool again.
If the current directory is same as the directory of the tool, see 7.7.6.3 (c) to identify the
symptom that corresponds to the output return code. After resolving the problem, run
the tool again.
The environment is invalid. (reason=reason)

The system environment is invalid.
(S) Stops processing.
(O) Re-install HTnM or the HTnM Agents. If you are still unable to resolve the
problem, see 7.7.5.3 to take appropriate action.
You do not have permission to execute the command.

Since you do not have permission to execute the command, you cannot execute it.
(O) After making sure that you have the right permissions to use the Store database
error detection tool, run the tool again.
You do not need to execute the command because the problem did not occur.
Standard output
You do not need to run the Store database error detection tool because no errors have
occurred in the environment.
The setup command is already running.

The Store database error detection tool cannot be used because the setup command is

running.
The start, stop or setup command is being executed.

The Store database error detection tool cannot be used because the start, stop, or
setup command is running.
Error occurred while deleting directory directory : return-code

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.
(O) Delete the directory-name directory.
[Error] Store version is invalid. (Store Version=store-version)

The Store database version in the definition file for the database being processed is
invalid. The definition file might be corrupted.
(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)

An attempt to lock the Store database has failed. The jpcresto command might be
accessing the Store database.
(O) Make sure that the jpcresto command is not being executed, and then
re-execute the command.

7.7.6.3 Return codes
This section contains return codes (rc = return-code) shown in messages and the
corresponding symptoms.
(a) Return codes that are output with the following message:
[Error] Backup processing failed. (rc = return-code)
# Return Error cause

code
1 0 Unknown
2 1 An argument is invalid.
3 2 You do not have permission to execute the command.
4 5 The HTnM server or Agents have not been installed.
5 10 The command is running.
6 100 HTnM environment settings are invalid.
7 104 The specified Master Store service, Agent Store service, or Remote
Monitor Store service is currently performing backups or is exporting
data.
8 200 There is not enough memory.
9 210 There is not enough disk space.
10 211 An attempt to access a file or directory has failed.
11 222 An error occurred in communication processing.
12 223 A timeout occurred in communication processing.
13 255 An unexpected error occurred.
(b) Return codes that are output with the following message:
[Error] Store version check processing failed. (rc= return-code)

code
1 -1 An attempt to access a file (jpcsto.ini) has failed.

(c) Return codes that are output with the following message:
[Error] DB check processing fails. (rc= return-code)

code
1 1 An argument is invalid.
2 2 You do not have permission to execute the command.
3 8 The data model version of Store database is invalid
4 200 There is not enough memory.
5 210 There is not enough disk space.
6 211 An attempt to access a file or directory has failed.
7 255 An unexpected error occurred.
(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)

code
1 -1 Unknown
2 -73 An attempt to access a lock file has failed.

7.8 How to confirm whether other programs are connected to HiRDB
If none of the following commands can stop HiRDB, other programs might be connected to HiRDB:
- 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.
cd /d Suite-installation-directory\Base\HDB\BIN
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.
Suite-installation-directory\Base\HDB\BIN
Suite-installation-directory\Base\HDB\CLIENT\UTL
Suite-installation-directory\Base64\HDB\BIN
Suite-installation-directory\Base64\HDB\CLIENT\UTL
< When the above paths are not added >

Execute the following command manually to add the paths. After executing the command, execute

"set PATH" command and confirm that the paths are added.
set
PATH=Suite-installation-directory\Base\HDB\BIN;Suite-installation-directory\Base\HDB\CLIENT\UTL;%
PATH%;
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.
Suite-installation-directory\Base\HDB
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.
set PDDIR=Suite-installation-directory\Base\HDB
set PDDIR=Suite-installation-directory\Base64\HDB
c) Execute "set PDCONFPATH" command and confirm that the result is following.
Suite-installation-directory\Base\HDB\CONF
Suite-installation-directory\Base64\HDB\CONF
< When the above character string is not defined in PDCONFPATH variable >
execute "set PDCONFPATH " command and confirm that the variable was defined correctly.
set PDCONFPATH=Suite-installation-directory\Base\HDB\CONF
[In Ver.8 or later ]
set PDCONFPATH=Suite-installation-directory\Base64\HDB\CONF
d) Execute "set PDUXPLDIR" command and confirm that the result is following.

Suite-installation-directory\Base\HDB\UXPLDIR
Suite-installation-directory\Base64\HDB\UXPLDIR
< When the above character string is not defined in PDUXPLDIR variable >
execute "set PDUXPLDIR" command and confirm that the variable was defined correctly.
set PDUXPLDIR=Suite-installation-directory\Base\HDB\UXPLDIR
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 HTNM server which is connected to the HDvM database
Ver.7 or later htm@<IP address> Note: In Ver.7 or later, IP address is displayed.
HBase - hostname HSCS products other than HTNM, or HTNM server
which is connected to its own database
******** A program in use by HiRDB. (This can be ignored.)
Unknown The programs below:
- HSCS products whose version is earlier than 6.4.0-00,
except HTNM.
- HTNM server(earlier than 6.4.0-00) which is connected
to its own database.
- Other products.
Example of pdls -d prc -a command execution results (Ver.6)

HOSTNAME : 127.0.0.1(173037)
STATUS PID UID GID SVID TIME PROGRAM C-PID
C-GRP
L 1531 0 1 _admrsvr 999999 ********

L 1532 0 1 _admrsvr 999999 ********
L 1533 0 1 _admrsvr 999999 ********
L 1534 0 1 _mlg 999999 ********
L 1535 0 1 _rdm 999999 ********
...
L 1552 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)
L 1553 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1554 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)
L 1555 0 1 sds01 135911 HBase-SFT5220-01 1388(127.0.0.1)
L 1560 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1561 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1562 0 1 sds01 121433 HBase-SFT5220-01 1388(127.0.0.1)
L 1563 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1564 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1565 0 1 sds01 121434 HBase-SFT5220-01 1388(127.0.0.1)
L 1566 0 1 sds01 135929 HBase-SFT5220-01 1388(127.0.0.1)
L 1567 0 1 sds01 135836 htm 1388(127.0.0.1)
L 1577 0 1 sds01 121509 Unknown 1388(127.0.0.1)

HOSTNAME : 127.0.0.1(173037)
C-GRP
L 1531 0 1 _admrsvr 999999 ********
L 1532 0 1 _admrsvr 999999 ********
L 1533 0 1 _admrsvr 999999 ********
L 1534 0 1 _mlg 999999 ********
L 1535 0 1 _rdm 999999 ********
...

L 1552 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)
L 1553 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1554 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)
L 1555 0 1 sds01 135911 HBase-SFT5220-01 1388(127.0.0.1)
L 1560 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1561 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1562 0 1 sds01 121433 HBase-SFT5220-01 1388(127.0.0.1)
L 1563 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1564 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1565 0 1 sds01 121434 HBase-SFT5220-01 1388(127.0.0.1)
L 1566 0 1 sds01 135929 HBase-SFT5220-01 1388(127.0.0.1)
L 1567 0 1 sds01 135836 htm@<IP address> 1388(127.0.0.1)
L 1577 0 1 sds01 121509 Unknown 1388(127.0.0.1)
Example of pdls -d prc -a command execution results (Ver.8 or later)

HOSTNAME : 127.0.0.1(173037)
C-GRP
L 1531 0 1 _admrsvr 999999 ********
L 1532 0 1 _admrsvr 999999 ********
L 1533 0 1 _admrsvr 999999 ********
L 1534 0 1 _mlg 999999 ********
L 1535 0 1 _rdm 999999 ********
...
L 4316 0 0 sds01 124629 HBase-HBase64StgMgmtSSOService 0(127.0.0.1)
L 5472 0 0 sds01 999999
L 6004 0 0 sds01 999999
L 2724 0 0 sds01 999999
L 4888 0 0 sds01 999999
L 5304 0 0 sds01 999999

[In Solaris]
database.
cd /opt/HiCommand/Base/HDB/bin
. ./pduxenv
Note: A space is needed between "." and "./pduxenv".
After executing "pduxenv" command, operate the following procedures a) d), then confirm that the
a) Execute "echo $PATH" command to confirm that the following path is added to the result.
/opt/HiCommand/Base/HDB/bin
< When the above path is not added >

Execute the following command manually to add the path. After executing the command, execute
"echo $PATH" command and confirm that the path is added.
PATH=/opt/HiCommand/Base/HDB/bin:$PATH;export PATH
b) Execute "echo $PDDIR" command and confirm that the result is following.
/opt/HiCommand/Base/HDB
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
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.
/opt/HiCommand/Base/HDB/lib
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
pdls -d prc -a
Ver.6 htm HTNM server which is connected to the HDvM database
Ver.7 or later htm@<IP address> Note: In Ver.7 or later, IP address is displayed.
except HTNM.
- Other products.

HOSTNAME : 127.0.0.1(173037)
C-GRP
L 1531 0 1 _admrsvr 999999 ********
L 1532 0 1 _admrsvr 999999 ********
L 1533 0 1 _admrsvr 999999 ********

L 1534 0 1 _mlg 999999 ********
L 1535 0 1 _rdm 999999 ********
...
L 1552 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)
L 1553 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1554 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)
L 1555 0 1 sds01 135911 HBase-SFT5220-01 1388(127.0.0.1)
L 1560 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1561 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1562 0 1 sds01 121433 HBase-SFT5220-01 1388(127.0.0.1)
L 1563 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1564 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1565 0 1 sds01 121434 HBase-SFT5220-01 1388(127.0.0.1)
L 1566 0 1 sds01 135929 HBase-SFT5220-01 1388(127.0.0.1)
L 1567 0 1 sds01 135836 htm 1388(127.0.0.1)
L 1577 0 1 sds01 121509 Unknown 1388(127.0.0.1)

HOSTNAME : 127.0.0.1(173037)
C-GRP
L 1531 0 1 _admrsvr 999999 ********
L 1532 0 1 _admrsvr 999999 ********
L 1533 0 1 _admrsvr 999999 ********
L 1534 0 1 _mlg 999999 ********
L 1535 0 1 _rdm 999999 ********
...
L 1552 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)
L 1553 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1554 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)

L 1555 0 1 sds01 135911 HBase-SFT5220-01 1388(127.0.0.1)
L 1560 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1561 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1562 0 1 sds01 121433 HBase-SFT5220-01 1388(127.0.0.1)
L 1563 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1564 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1565 0 1 sds01 121434 HBase-SFT5220-01 1388(127.0.0.1)
L 1566 0 1 sds01 135929 HBase-SFT5220-01 1388(127.0.0.1)
L 1577 0 1 sds01 121509 Unknown 1388(127.0.0.1)
[In Linux]
database.
cd <Hitachi Command Suite Common Component installation directory>/HDB/bin
. ./pduxenv
Note: A space is needed between "." and "./pduxenv".
After executing "pduxenv" command, operate the following procedures a) d), then confirm that the
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
< When the above path is not added >

"echo $PATH" command and confirm that the path is added.
PATH=/opt/HiCommand/Base/HDB/bin:$PATH;export PATH
b) Execute "echo $PDDIR" command and confirm that the result is following.
/opt/HiCommand/Base/HDB
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
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
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
pdls -d prc -a
Ver.7 or later htm@<IP address> HTNM server which is connected to the HDvM database
Note: IP address is displayed.

except HTNM.
- Other products.

HOSTNAME : 127.0.0.1(173037)
C-GRP
L 1531 0 1 _admrsvr 999999 ********
L 1532 0 1 _admrsvr 999999 ********
L 1533 0 1 _admrsvr 999999 ********
L 1534 0 1 _mlg 999999 ********
L 1535 0 1 _rdm 999999 ********
...
L 1552 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)
L 1553 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1554 0 1 sds01 121441 HBase-SFT5220-01 1388(127.0.0.1)
L 1555 0 1 sds01 135911 HBase-SFT5220-01 1388(127.0.0.1)
L 1560 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1561 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1562 0 1 sds01 121433 HBase-SFT5220-01 1388(127.0.0.1)
L 1563 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1564 0 1 sds01 135834 HBase-SFT5220-01 1419(127.0.0.1)
L 1565 0 1 sds01 121434 HBase-SFT5220-01 1388(127.0.0.1)
L 1566 0 1 sds01 135929 HBase-SFT5220-01 1388(127.0.0.1)
L 1577 0 1 sds01 121509 Unknown 1388(127.0.0.1)
Example of pdls -d prc -a command execution results (Ver.8 or later)

HOSTNAME : 127.0.0.1(173037)

C-GRP
L 1531 0 1 _admrsvr 999999 ********
L 1532 0 1 _admrsvr 999999 ********
L 1533 0 1 _admrsvr 999999 ********
L 1534 0 1 _mlg 999999 ********
L 1535 0 1 _rdm 999999 ********
...
L 5472 0 0 sds01 999999
L 6004 0 0 sds01 999999
L 2724 0 0 sds01 999999
L 4888 0 0 sds01 999999
L 5304 0 0 sds01 999999

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:

[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>(###)
Main Console HiRDB connections
NO STATUS PID UID GID SVID TIME PROGRAM C-PID C-GRP
24 L(RUN) 5400 0 0 sds01 190205 htm 0(<HTnM server IP address>)
< Ver.7>
"C:\Program Files\HiCommand\Base\HDB\bin\pdprcsls" Main Console HiRDB connections

24 L(RUN) 5400 0 0 sds01 190205 htm@<HTnM server IP address> 0(<HTnM server IP address>)

HiCommand_log_64.hdb\HDB_DetailLog\Initial\pdinfoget_<hostname>_init_04141
or
[HiCommand_log_64.hdb\HDB_DetailLog\Detail\PDDIR\spool\cnctusrdtl]
"C:\Program Files\HiCommand\Base64\HDB\bin\pdprcsls" Main Console HiRDB connections

For a Solaris HDvM host:

or
[HiCommand_log.hdb\HDB_DetailLog\Detail\PDDIR\spool\cnctusrdtl]
<Ver.6>
/opt/HiCommand/Base/HDB/bin/pdprcsls Main Console HiRDB connections

< Ver.7 >
/opt/HiCommand/Base/HDB/bin/pdprcsls
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 ]
or
[HiCommand_log.hdb\HDB_DetailLog\Detail\PDDIR\spool\cnctusrdtl]

/opt/HiCommand/Base/HDB/bin/pdprcsls
[In Ver.8 or later]

[HiCommand_log_64.hdb\HDB_DetailLog\Initial\pdinfoget_<hostname>_init_0414182746\pdinf
oget.sysinf.######]
or
[HiCommand_log_64.hdb\HDB_DetailLog\Detail\PDDIR\spool\cnctusrdtl]
/opt/HiCommand/Base64/HDB/bin/pdprcsls
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
- In Ver.7
- In Ver.8

For a Windows HDvM host:
[HiCommand_log\base\netstatlist]
- In Ver.8 or later
[HiCommand_log_64\base\netstatlist]
Port numbers used by the HTnM server when connecting to HDvM
IP address of the HTnM server host
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
For a Solaris HDvM host:

Local Address Remote Address Swind Send-Q Rwind Recv-Q State
IP address of the HTnM server host Port numbers used by the HTnM server when connecting to HDvM
-------------------- -------------------- ----- ------ ----- ------ -------
10.208.147.23.40890 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
For a Linux HDvM host:

- In Ver.7.1 to earlier than 8
- In Ver.8 or later
[HiCommand_log_64\base\netstatlist]
IP address of the HTnM server host Port numbers used by the HTnM server when connecting to HDvM
Local Address Remote Address Swind Send-Q Rwind Recv-Q State

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

7.9 Adding an OUI Code (Switch Agent version 7.1 or later)
If Switch Agent connects to a Brocade (SMI Agent for FOS) or Brocade (SMI Agent for EOS)
switch, the Agent generates a record only when the WWN of the switch contains a specific OUI code.
If a new OUI code is assigned to a vendor, no record is generated for switches in the monitored
fabric that have the new OUI code.
In Switch Agent version 7.1 or later, you can monitor switches with new OUI codes by adding the
new OUI code to the OUI codes file.
To add an OUI code to the OUI codes file, follow steps 1-4.
Step 1: Stop the Switch Agent instance.

Execute the jpcstop command to stop the instance.
- In Windows:
- In Solaris,Linux:
Step 2: Edit the OUI codes file.

Use a text editor to open the OUI codes file, add the new OUI code, and save the file. If there is no
OUI codes file, perform an overwrite installation of Switch Agent and then perform this step. Table
7.9-1 shows the file names and locations of the OUI codes file.
Table 7.9-1: File names and locations of the OUI codes file
No Connection target File name of the Location of the OUI codes file
OUI codes file
1 Brocade ouilist_fos.dat In Windows:
(SMI Agent for FOS) Suite-installation-directory\TuningManager\jp1pc\agtw\agent
2 Brocade ouilist_eos.dat In Solaris, Linux:
(SMI Agent for EOS) /opt/jp1pc/agtw/agent

OUI code file editing example (adding OUI code 006069):
#Add the OUI code of the Brocade(B-Model) switch which wants to be monitored by Agent for SAN Switch.
#For example: Add the OUI code line
#00051E - Six hexadecimal characters (0-9, A-F, a-f )
- Must end with a newline code or EOF.
006069
Step 3: Start the Switch Agent instance.

Execute the jpcstart command to start the instance.
- In Windows:
- In Solaris,Linux:
Step 4: Check the contents of the OUI codes file.

Check that the message shown in Table 7.9-3 is output to the log file of the Switch Agent instance
when the Switch Agent starts up.
Table 7.9-2: Path to the log file of a Switch Agent instance

No OS Log file path
1 Windows Suite-installation-directory\TuningManager\jp1pc\agtw\agent\<instance
name>\log\msglog*
2 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
1 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.

- 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
1 OUI codes file is not found. (file=<file Warning The file <file Perform an overwrite
name>, errcode=<error code>) name> does not installation of Switch
exist. Agent.
2 OUI codes file is incorrect. (file=<file Warning Failed to read the Delete the file <file
name>, errcode=<error code>) file <file name>. name> and perform an
overwrite installation of
Switch Agent.
3 OUI code definition is incorrect. Warning The line added to Check that the OUI code
(file=<file name>, line=<line the OUI codes added on the line <line
number>, errcode=<error code>) file is incorrect. number> consists of six
hexadecimal characters.
If not, correct the OUI
code.
4 The number of lines has reached the Warning The OUI codes Delete unnecessary lines
maximum. (file=<file name>, file exceeds the so that the number of
maximum_number_of_lines=1024) maximum lines in the OUI codes
number of lines. file does not exceed
1024.
5 The switch with the OUI code not Warning The OUI code Check that the OUI code
defined was detected.
(WWN=<WWN of the switch added to the OUI added to the OUI codes
added to be monitored>) codes file does file is correct. If it is not
not match the correct, add the correct
OUI code of the OUI code.
switch added for
monitoring.

Note: Default OUI codes monitored by Switch Agent
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
Agent for SAN Switch version
Brocade
v6.3.0
No (B-Model) 6.0.0 7.1.0
6.1.0 6.2.0 6.3.0-01 7.0.0
OUI code (#1) 6.3.0-00 or later
or later
1 00051E Y Y Y Y Y Y Y
2 006069 Y Y Y Y Y Y Y
3 000533 N N N N Y Y Y
4 0027F8 N N N N N N Y
5 50EB1A N N N N N N Y
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
Agent for SAN Switch version
Brocade (M-Model) OUI
No 7.1.0
code 6.2.0 6.3.0 7.0.0
or later
1 080088 Y Y Y Y
Legend:
Y: This OUI code can be monitored with Switch Agent.
N: This OUI code cannot be monitored with Switch Agent.

7.10 Overview of Agent Common Component
When HTnM - Agent is installed, a component called Agent Common Component that provides
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.

7.11 About Agent for RAID Extention component
In Windows Server 2008 or Linux environment, installation of Agent for RAID v7.4
or later is also install Agent for RAID Extention component simultaneously. Agent
for RAID Extention component is a component with a linkage function with Hitachi
Command Director Software.
Agent for RAID Extention component is deployed to the following directory.

(Windows) : <Agent for RAID installation folder>\agtd\AgentforRAIDExtension
(UNIX) : /opt/jp1pc/agtd/AgentforRAIDExtension
The success or failure of installation of Agent for RAID Extention component can be
checked by the following logs.
Agent for RAID installation log file: HTM_INST_LOG_AGTD_*.log
file path
(Windows) : %SystemDrive% folder
(UNIX) : /var/opt/HiCommand/TuningManager/logs/ directory
output messages
The RAE installation will now start.
The RAE installation ended. (exit code=<exit code> *)
*: When a completion code is except zero, installation has gone wrong.
On troubleshooting material of installation of Agent for RAID Extention, refer to

the support portal on the HDS Loop(http://loop.hds.com/groups/hcmd-support).

7.12 Analytics tab
7.12.1 Internal architecture

Figure 7.12.1-1 shows an overview of the internal architecture behind the Analytics tab.
HTnM-Server JDBC(type4)/Hibernate HDvM AnalyticsTab

RMI
HTnM-TS HTnM-PR HTnM-MC

VSA
PFM-SDK Lib
(View Server Access) HiRDB VSA
HiRDB REST Accessor
(View Server Access)
Configuration
NS-API (TCP/IP) Capacity
PQL/Performance DATA http
RMI
HTnM-Server
HTnM-CM HTnM-Server
View Server Correlator Trap Generator HC-Agent Store REST API Component
Name Server Master Manager
Node Management Main Server View I/F Event Processor SNMP
PFM-SDK Lib PFM-SDK Lib PFM-SDK Lib PFM-SDK Lib
PFM-SDK Lib PFM-SDK Lib
Status Server Master Store PFM-SDK Lib

Alert Event Store HC Agent
PFM-SDK Lib PFM-SDK Lib Collector
Action Handler
Action Invoker StoreDB StoreDB
PFM-SDK Lib
Alert Event Service
Configuration
http
HTnM-Agents
PFM-SDK Lib PFM-SDK Lib PFM-SDK Lib PFM-SDK Lib HTnM-Agent
Status Server Agent Store Agent Collector Action Handler REST API Component
Monitored

Systems
StoreDB

Performance
File
Configuration
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.
7.12.2 Related properties files and log files

7.12.2.1 Property files
Table 7.12.2.1-1 lists the property files related to the Analytics tab.
Table 7.12.2.1-1 Property files
No. Property file File location Description
1. tuningmanager.properties <HDvM Install Directory>\config Defines settings for communication

with HTnM server.
2. server.properties <HDvM Install Directory>\config Defines settings for the functions of

the Analytics tab (such as email
notification).
3. config.xml <HDvM Install Directory>\HiCommandServer\ Defines communication settings for
vsa\conf collecting the following information
from HTnM server:
- Configuration information
- Performance information (for
health checks)
4. configforclient.xml Defines communication settings for
collecting the following information
from HTnM server:
- Performance information (for the
performance-problem
determination wizard)
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.
7.12.2.2 Log files

Table 7.12.2.2-1 lists the log files related to the Analytics tab.
Table 7.12.2.2-1 Log files

No. Log file (*1) File location Description
1. WebServiceMessage.log.n <HDvM Install Directory>/HiCommandServer/ Logs that the store messages and trace
WebServiceTrace.log.n logs log data that are output by HDvM
GUI 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

via the Tuning Manager API.)
2. HDvMtracen.log <HDvM Install Directory>/HiCommandServer/ Logs that store the trace log data that
trace.log logs is output by HDvM server.
(The log data to be stored includes the
log data that is output when HDvM
accesses the Tuning Manager server
via the Tuning Manager API.)
3. vsaTracen.log <HDvM Install Directory>/HiCommandServer/ Trace logs that are output by HDvM
vsaTraceForClientn.log vsa/logs when HDvM accesses HTnM Server
via the VSA.
4. jpclog [HTnM server & HTnM Agent for RAID] Message logs that are used by HTnM
<HTnM Install Directory>/jp1pc/log CM and HTnM Agent.
5. msglog [HTnM server] Message and communication logs for
nslog <HTnM Install Directory>/jp1pc/mgr/viewsvr/log HTnM CM and HTnM Agent.
[HTnM Agent for RAID]
<HTnM Install Directory>/jp1pc/agtd/store/
<InstanceName>/log/
<HTnM Install Directory>/jp1pc/agtd/agent/
<InstanceName>/log
6. htmRestMessagen.log <HTnM Install Directory>/logs Message logs or trace logs that are output by
htmRestTracen.log HTnM Agent when HDvM uses the Tuning
htmRestErrorDetailn.log Manager API to access the Tuning Manager
server. (*2)
7. htmRestAgtMessagen.log <HTnM Install Directory>/jp1pc/htnm/logs Message logs or trace logs that are output by
htmRestAgtTracen.log HTnM Agent when the Tuning Manager
server uses the Tuning Manager API to
access HTnM Agent.
(*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 Symptom that can occur
1. System environment Communication between HDvM and HTnM server fails.

settings Communication between HTnM server and HTnM Agent fails.
Reception of information from HTnM Agent fails (due to a cause
other than a communication failure).
2. HDvM property settings Communication between HDvM and HTnM server fails.
3. HTnM - Agent settings Reception of information from HTnM Agent fails (due to a cause
other than a communication failure).
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 Reviewing the system environment settings

If there are problems with the system environment settings, communication between servers might
fail, or reception of information from HTnM Agent might fail. The following describes the points
to be reviewed when you encounter such a problem.
7.12.3.1.1 Date and time settings on server machines

A) The GMT-based time settings of the computers that run HDvM server, HTnM server, and
HTnM Agent must be the same (with a difference of 5 or fewer minutes).
Point to be reviewed:
Check and compare the GMT-based time settings that are specified on the servers.
Action (example):
Take action as described in the section About machine time differences of the following
manual:
- In Ver.7
- In Ver.8
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.
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
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.
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.
7.12.3.2 Reviewing the HDvM property settings

If there are problems with the HDvM property settings, communication between HDvM and
HTnM server might fail. The following describes the points to be reviewed when you encounter
such a problem.
7.12.3.2.1 Property settings specified in the tuningmanager.properties file

A) In an environment in which HDvM server and HTnM server are installed on different
computers, or in an environment in which multiple HTnM servers are connected to one
HDvM server, the HTnM server information must be correctly set for the following
properties:
- htnm.servers
- htnm.server.n.host
- htnm.server.n.protocol
- htnm.server.n.port
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

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.
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.
7.12.3.2.2 Property settings in the config.xml and configforclient.xml files

A) If the computer on which HDvM server is installed has multiple NICs, or if a firewall is
enabled on the computer on which HTnM server is installed, the correct HDvM server or
HTnM server information must be specified for the following properties:
- ownHost
- ownPort
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.)
 This line must be removed.

This line must be removed.
Figure 7.12.3.2.2-1 Example of the config.xml file
7.12.3.3 Reviewing the HTnM - Agent settings

If there are problems with the HTnM Agent settings, reception of information from HTnM Agent
might fail. The following describes the points to be reviewed when you encounter such a problem.
7.12.3.3.1 Settings of data collection target resources in HTnM Agent for RAID
HTnM Agent for RAID must be set to collect the resource-configuration and performance data
that is needed for the analysis function of the Analytics tab.
See case study SD4952860. In this case, the problem was corrected by specifying the following
entry: "unassigned Open Volume Monitoring=Y"

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.
7.12.3.3.2 Data collection interval settings in HTnM Agent for RAID

In HTnM Agent for RAID, proper values must be specified for the data collection interval settings
in order not to skip collection of data for any resources. If there are too many resources in the
storage system, collection of data might sometimes be skipped. If collection of data is skipped,
message KAVE00213-W is output to the HTnM Agent log. For details, see Appendix 13
Recommended action when the KAVE00213-W message is output and when performance data
collection is skipped.
Review the record-data collection interval.

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)
2) The Analyze MP Blades/Units window opens,and an attempt to obtain storage information

from HTnM fails, and error messages KAIC18468-E and KAIC08850-E are displayed.
messages:
Unable to collect information from Tuning Manager. (host name = host-name, agent

name = agentname, record name = recordname, 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)) (KAIC18468-E)
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

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 URI example
1. HDvM http://127.0.0.1:22015/TuningManager/internal/v1/objects/AgentForRAID
(the Analytics tab
or the Replication
tab)
2. User programs http://127.0.0.1:22015/TuningManager/v1/objects/AgentForRAID

7.13 Notes on removal
7.13.1 Processes might remain after removal
If you remove HTnM product in a UNIX environment in which the IP address cannot be resolved
from the host name, processes might remain. In version 7.6.1 or later, this symptom might also
occur if you changed the host name without following the correct procedure. If this symptom
occurs, use the kill command to terminate all processes whose names begin with jp1pc.
If this symptom occurs during removal of Agent, either of the symptoms shown below might also
occur. If either of these symptoms occurs, resolve the IP address from the host name, re-install
Agent, and then remove Agent again.
Symptoms that might occur during removal of Agent:

a) A message that reports that removal succeeded is output, but files remain in the installation
directory.
b) Removal fails with the following message:
"This product cannot be removed because one or more Agents whose versions are 5.5 or earlier
have been installed on this host. Before removing this product, upgrade the Agents to version
5.7 or later, or remove them."
7.14 Notes on using NAS Agent to monitor HNAS

To collect performance data from HNAS, use the HNAS rusc command. If the rusc command is
issued from multiple monitoring sources, a competitive error occurs, and data is not collected
correctly. In such a case, the KAVF24165-W message is output to the common message log, and the
performance values for NAS Agent might be invalid.
For more details, see the following manual:
- Hitachi Command Suite Tuning Manager Agent Administration Guide

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.

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
1 The microcode version of a storage system is not supported 7.15.3.1
2 Other processes are logged in to a storage system with the same user ID 7.15.3.2
3 Other processes are collecting performance data from a storage system 7.15.3.3
4 Memory is insufficient 7.15.3.4
7.15.3.1 The microcode version of a storage system is not supported

How to check this:
Execute the jpctdchkinst command on the instance that monitors the storage system. If the
microcode version is not supported, the following message will be output:
KAVF18823-E The SVP version of the storage system is not supported.
In addition, if an Agent instance has already started, the following message will be output to a log
file.
Table 7.15.3.1-1 Messages output to a log file

# Log file* Details of output
1 pmmcChkSvpTrace[n].log KATR25044-I I CheckSvpVersion#main(161) check svp version.

(destination: {version of the connected SVP} , supported:{the earliest
version of the supported SVP})
KATR25044-I I CheckSvpVersion#main(164) the storage svp
version is not supported. (storage:{information about the connected
storage system})
*: Location of the Log file:
Agents-installation-directory\agtd\instance-Name\log
Action to be taken:
Upgrade the microcode version of the monitored storage system to a supported version.

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.
Table 7.15.3.2-1 Messages output to log files

1 pmmcChkSvpTrace[n].log The following stack trace will be output together with an error message
2 pmmcGetdkcinfTrace[n].log and warning message:

sanproject.serverux.data.SANRmiException: 1 - 5132 , 1 - 5132 , 1
3 pmmcCollectorTrace[n].log
5132
*Location of the log file:
Agents-installation-directory\agtd\instance-Name\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.
Table 7.15.3.3-1 Messages output to log files

1 pmmcChkSvpTrace[n].log The following stack trace will be output together with an error message
2 pmmcGetdkcinfTrace[n].log and warning message:

sanproject.serverux.data.SANRmiException: 1 - 5400 , 1 - 5400 , 1
3 pmmcCollectorTrace[n].log
5400
*Location of the Log file:
Agents-installation-directory\agtd\Instance-Name\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.

7.15.3.4 Memory is insufficient
How to check this:
If the Java heap memory becomes insufficient while performance data is being collected by using
a TCP/IP connection, collection of performance data fails, after which the following file is
created:
Agents-installation-directory\agtd\instance-Name\log\hprof-dumps.hprof
In this case, java.lang.OutOfMemoryError might be output to the following:

Agents-installation-directory\agtd\instance-Name\log\pmmcCollectorTrace.log
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.

Appendix 1 List of metric
This document describes what record/field of Agent is used for showing data in Main Console. If
you want to check source data which used for showing metric in Main Console, first check what
record/field of Agent is used by using this document, then show report by using Performance
Reporter.
In Ver.6
In Ver.7
In Ver.7.1
In Ver.8
Appendix1_V8_metri
cs.zip
Appendix 2 Resource estimate tool

HTnM Version 6 or later does not support this tool.

Appendix 3 Tuning Manager Deletion Procedures
3-a Uninstall of the Tuning Manager server for Windows(Ver.5.1 to Ver.5.9)
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

Tuning Manager server for Windows 6.0.0-00 to earlier than 8.0.0
Note: This document applies only to the HDS version.
3-b.3 Overview of deleting Tuning Manager server

Figure 3-b.3-1 shows an overview of the process for deleting Tuning Manager server.

Start
Forcibly Deleting Tuning Manager server
Do you want to perform Stopping services related to Tuning Manager server

an uninstallation that leaves NO
Agents?
YES
Performing the preprocessing for uninstalling components
Uninstall the Tuning Manager server The agents must also be
without uninstalling Agents
uninstalled
Uninstalling the Collection Manager component
NO
Was the uninstallation successful?
Uninstalling the Tuning Service component
YES
Normal uninstallation procedure Uninstalling the Performance Reporter component
NO
Was the uninstallation Uninstall the Hitachi Storage Command Suite common component
successful?
YES
YES Deleting the database files
Can the user fix the error?
NO Deleting directories and registry keys
End
Restarting the OS
End Delete HiCommand Device Manager authentication information
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.

- 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.
# Notation used in text On a 64-bit OS

1 %SystemRoot%\system32 %SystemRoot%\SysWow64
2 %ProgramFiles% %ProgramFiles(x86)%
HKEY_LOCAL_MACHINE\SOFTWARE\ HKEY_LOCAL_MACHINE\SOFTWARE\
3
Wow6432Node

3-b.4 Deleting Tuning Manager server without deleting Agent
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 CM_NOUNINST 1
(2) Restarting the OS
Restart the OS to apply the environment variable in (1).
(3) Uninstalling Tuning Manager server.
Uninstall Tuning Manager server. When Tuning Manager server is successfully uninstalled, the
following window appears.
Figure 3-b.4-1: Window that appears when Tuning Manager server is successfully uninstalled

(4) Environment variable deletion.
Delete the following environment variable:
# Environment variable name

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

3-b.5 Forcibly Deleting Tuning Manager server
If there is a registry deletion command (htnmsvrregclean.bat) that is supported
by Tuning Manager server (note that Windows 2000 is not supported), follow the
procedure described in 3-b.5.1. If there is no command, follow the procedure described in
3-b.5.2 to forcibly delete Tuning Manager server manually. If you are using Windows
2000, forcibly delete Tuning Manager server manually.
# Tuning Manager server version Registry deletion command version

1 6.0.0 or later 1.0.0-00
3-b.5.1 Procedure for using the registry deletion command
3-b.5.1.1 Terms
# Terms Directory
Hitachi Storage %ProgramFiles%\HiCommand\Base

1
Command-Suite-Common-Component-installation-directory
2 Hitachi-Tuning-Manager-installation-directory %ProgramFiles%\HiCommand\TuningManager
3 installation-directory %ProgramFiles%\HiCommand
Note: Unless you specify other directories during installation, the above
directories are used by default.
3-b.5.1.2 Stopping services related to Tuning Manager server

(1) Execute the commands to stop the services.
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-b.5.1.2.
# Directory
1 Hitachi Storage Command-Suite-Common-Component-installation-directory\bin
b) Execute the command indicated below.
If the hcmdssrv command does not exist, go to step (1) d) in section 3-b.5.1.2.
# Command
1 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
1 hcmdssrv /status
Example of the output
KAPM05009-I Already stopped service. service-name=HiCommand Performance Reporter
KAPM05009-I Already stopped service. service-name=HiCommand Suite TuningService
KAPM05009-I Already stopped service. service-name=HiCommand Suite TuningManager
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Common Service
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Web Service
KAPM06441-I The HiRDB service has already stopped.
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.1.2.
d) Move to the directory indicated below.
If the directory does not exist, go to step (2) in section 3-b.5.1.2.
# Directory
1 Hitachi-Tuning-Manager-installation-directory\jp1pc\tools
e) Execute the command indicated below.
If the jpcstop command does not exist, go to step (1) f) in section 3-b.5.1.2.
# Command
1 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)
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.1.2.
Even if Inactive* is not displayed (and another string, such as Active, is displayed
instead), go to step (2) in section 3-b.5.1.2.
# Command
1 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.
--------- --------- ------------- -------- -------- --------
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*

displayed.
Note: The asterisk (*) in Inactive* might not be displayed.
(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.
# Hitachi Storage Command Suite related service

1 HBase Storage Mgmt Common Service
2 HBase Storage Mgmt Web Service
3 HBase Storage Mgmt Web SSO Service

4 HiCommand Performance Reporter
5 HiCommand Suite TuningManager
6 HiCommand Suite TuningService
7 HiRDB/ClusterService _HD0
8 HiRDB/EmbeddedEdition _HD0
9 PFM - Action Handler
10 PFM - Agent for HealthCheck
11 PFM - Agent Store for HealthCheck
12 PFM - Correlator
13 PFM - Master Manager
14 PFM - Master Store
15 PFM - Name Server
16 PFM - Status Server
17 PFM - Trap Generator
18 PFM - View Server
(3) Reboot the OS
a) Reboot the OS.
3-b.5.1.3 Performing the preprocessing for uninstalling components

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

# Directory
If the hcmdsweb2 command does not exist, go to step (3) in section 3-b.5.1.3.
# Command
1 hcmdsweb2 /delete /type TuningManager
2 hcmdsweb2 /delete /type PerformanceReporter
If the message KAPM04202-I(the command executed successfully) or

KAPM04118-E(the program is already deleted) is displayed, go to step (3) in section
3-b.5.1.3.
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-b.5.1.3.
(3) Delete the Tuning Manager server installation control information.
a) Execute the command indicated below.
If the hcmdscancel command does not exist, go to step (4) in section 3-b.5.1.3.
# Command
1 hcmdscancel TuningManager
(4) Delete the file.
a) Make sure that the following file does not exist.
If the file exists, delete it manually.
If the file does not exist, go to section 3-b.5.1.4.
# File Name
1 %SystemDrive%\htmpruninst.rtn
3-b.5.1.4 Uninstalling the Collection Manager component

If you are using Windows Server 2003, perform the procedure described in step (1) in
section 3-b.5.1.4. If you are using Windows Server 2008, perform the procedure
described in step (2) in section 3-b.5.1.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 section 3-b.5.1.5.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
d) Copy the value of the UninstallString entry of the registry key.
e) Paste the copied value into the command prompt window, and then execute this
command to start the uninstallation.
Note: Make sure that the Services applet is closed when executing the uninstaller.
f) When the uninstallation finishes, go to section 3-b.5.1.5.
b) Open the following file by using a text editor.

# File Name
1 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.
# Registry Key
<Collection Manager-GUID>
e) Copy the value of the UninstallString entry of the registry key.

f) Paste the copied value into the command prompt, add the following option, and
then execute the command. The uninstallation will start.
# Command to execute
1 {UninstallString-command}/qn+ ( represents a one-byte space)
Note: If the uninstallation terminates successfully, the following dialog box

indicating such is displayed. Click OK to close the dialog box.
Figure 3-b.5.1.4-1: Successful uninstallation termination window
Because no windows are displayed during an uninstallation, no user responses

are required.
Note: Make sure that the Services applet is closed when executing the
uninstaller.
g) After executing the uninstaller, go to section 3-b.5.1.5.
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.1.12.
3-b.5.1.5 Uninstalling the Tuning Service component

(1) Execute the Tuning Service uninstaller.
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-b.5.1.6.
# Registry Key
{89331AB6-2E76-4986-9458-54795EF060A0}
c) Copy the value of the UninstallString entry of the registry key.
d) Paste the copied value into the command prompt window, and then execute this
command to start the uninstallation.
Note: Because no uninstaller window is displayed, no user input is required.

3-b.5.1.6 Uninstalling the Performance Reporter component

(1) Execute the Performance Reporter uninstaller.
b) Start the registry editor and make sure that the registry key indicated below
exists.
# Registry Key
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
d) Paste the copied value into the command prompt window, and then execute this
command with the option shown below to start the uninstallation.
1 {UninstallString-value}/NOREBOOTNOFLAGOFF (: a single-byte space)
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
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.
# File
Hitachi Storage
1
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.
# Command line
1 HBuninst /X
d) After the dialog box that indicates termination of the command appears, check
the value that was output to the following file.
# File
1 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 Executing the registry deletion command

(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, the command might not operate correctly.
If you are using Windows Server 2008 or later (Windows v6 or later), use an
elevated command prompt to execute the command. To start an elevated command
prompt, right-click the command prompt icon, and then choose Run as
administrator from the context menu.
- Do not execute programs (such as installers or registry editors) that access the
registry.
- Do not attempt to start the registry deletion command again if it already has been
started.
- During execution, do not cancel the registry deletion 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.
- Only execute the registry deletion command when there is at least 100 KB of
available space (required for the log file) on the system drive. If the log file already
exists, confirm that the file is write-enabled, and then execute the command.
- Note that the htm-getlogs command does not collect the log file that is

generated when the registry deletion command is executed.
- The log file is not automatically deleted. If the file is no longer needed, perform
the forced uninstallation procedure, and then manually delete the file.
(2) Open a command prompt.

(3) Execute the registry deletion command (htnmsvrregclean.bat). You will be asked
if you want to continue. Enter y.
Removal of the registry keys for HTnM Server will now start.
Do you want to continue? (y/n)
(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.
Press the Enter key to terminate the htnmsvrregclean.bat. command.

- If the end code is 0, go to section 3-b.5.1.9.
- If the end code is not 0, go to step (5) in section 3-b.5.1.8.
(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
1 %SystemDrive%\htnmsvrregclean.log
The possible causes of the errors are described below.

Refer to the end code and then re-execute the command.
If you re-execute the command and the end code is still not 0, open the above file and
check which registry entries could not be deleted. Delete these manually.
# End Error Cause Action

code
1 1 Registry In the access permission Disable the Deny setting in Delete
deletion failed. settings for the registry key, Permission of the access permission

Deny has been specified for settings for the registry key, and then
Delete Permission. re-execute the command.
2 The registry key to be deleted The registry key to be deleted might
has been locked. be locked while an HTnM operation is
being switched over, such as when a
service is being started. Using the
service control manager, specify
Manual as the Startup type for
agent-related services. Reboot the OS,
and then re-execute the command.
3 You do not have administrator Right-click command prompt icon, and
privileges. An unelevated then choose Run as administrator to
command prompt (one that start an elevated command prompt.
does not have administrator Then, use the elevated command
privileges) was used to execute prompt to re-execute the command.
the command in Windows 2008
or later.
4 You do not have administrator Log in as a user that belongs to the
privileges. This user does not Administrators group, and then
belong to the Administrators re-execute the command.
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.
# Shared file name

1 %SystemRoot%\system32\htmjpccomm.dll
2 %SystemRoot%\system32\jpcaudit{vvrrss}.dll
3 %SystemRoot%\system32\jpccomm{vvrrss}.dll
4 %SystemRoot%\system32\jpccommhcc.dll
5 %SystemRoot%\system32\jpccoommhccjp.dll
6 %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
Storage Command Suite.

If the following directories exist, delete them manually.
# Directory
1 %temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
2 %SystemDrive%\_HDBInstallerTemp
(3) Delete the Tuning Manager server database files.

a) Open the files indicated below.
If the files do not exist, go to step (4) in section 3-b.5.1.10.
# File name
1 Hitachi-Tuning-Manager-installation-directory\inst\db_area.properties
2 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
1 db_areapath1
2 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-b.5.1.10.
(4) 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.1.3.
If the directory does not exist, go to step (5) of section 3-b.5.1.10.
If no file existed in step (1) a) of section 3-b.5.1.3, go to step (5) of section 3-b.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-b.5.1.11.
# Directory
1 <Installation directory>

%ProgramFiles%\InstallShield Installation Information\
2
{89331AB6-2E76-4986-9458-54795EF060A0}

3
{639938A4-41F1-4643-B5E9-05B1CAC6DA21}

4
{465EF71F-B608-4C33-9E19-D56DDCADC82A}

5
{1345FCD1-713E-4449-8F76-3F6503941040}

6
{61577C30-8F2D-445E-9E9F-54F65EE419A5}

7
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
3-b.5.1.11 Deleting HiCommand Device Manager authentication information

The procedure described in this section applies only when the instance of Tuning
Manager server you forcibly deleted was connected to an instance of HiCommand
Device Manager on a remote host. This procedure must be performed on the remote
host.
Perform this procedure only after making sure that no Hitachi Storage Command
Suite family of products other than the forcibly deleted instance of Tuning Manager
server have been specified as connection destinations for the target instance of
HiCommand Device Manager.
(1) Delete the HiCommand Device Manager authentication information.
If this directory does not exist, go to section 3-b.5.1.12.
# Directory
If the hcmdsintg command does not exist, go to section 3-b.5.1.12.
# Command line
hcmdsintg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ"
1
( 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.1.12.
Output example

Primary Server : 127.0.0.1
Product Name :
DeviceManager
ProvisioningManager
TuningManager
c) Execute the following command.
# Command line
hcmdsintg /delete /type TuningManager /user "htnmrepuser" /pass
1
"INTERNALHRXJIHVZ" ( represents a one-byte space)
d) Execute the command indicated below. Make sure that TuningManager is not
included in the output results.
# Command line
hcmdsintg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ"
1
( represents a one-byte space)
3-b.5.1.12 Installation and uninstallation of Tuning Manager server

The procedure of forcibly delete Tuning Manager server is completed in section
3-b.5.1.11. However, if any of the following conditions are met, the additional procedure
described in this section must be performed.
The file does not exist in step (2) b) of section 3-b.5.1.4.
The uninstallation of Collection Manager fails in (2) g) of section 3-b.5.1.4.
If any of the above conditions are met, some of the information of Tuning Manager server
might remain. Therefore, perform the following procedures sequentially to delete
the information of Tuning Manager server completely.
After forcibly delete Tuning Manager server, install Tuning Manager server .
After the installation is finished normally, uninstall Tuning Manager server by
selecting the Programs and Features menu in the Control Panel.
3-b.5.2 Procedure for manually deleting registry entries
3-b.5.2.1 Terms
# Terms Directory
Hitachi Storage %ProgramFiles%\HiCommand\Base

1
Command-Suite-Common-Component-installation-directory
2 Hitachi-Tuning-Manager-installation-directory %ProgramFiles%\HiCommand\TuningManager
3 installation-directory %ProgramFiles%\HiCommand
Note: Unless you specify other directories during installation, the above directories are

used by default.
3-b.5.2.2 Stopping services related to Tuning Manager server

If the directory does not exist, go to step (1) d) in section 3-b.5.2.2.
# Directory
If the hcmdssrv command does not exist, go to step (1) d) in section 3-b.5.2.2.
# Command
1 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
1 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.
# Directory
1 Hitachi-Tuning-Manager-installation-directory\jp1pc\tools

If the jpcstop command does not exist, go to step (1) f) in section 3-b.5.2.2.
# Command
1 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
f) Execute the command indicated below and make sure that Inactive* is displayed for the
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),
go to step (2) in section 3-b.5.2.2.
# Command
1 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.
--------- --------- ------------- -------- -------- --------
XXXX PH1XXX Action Handler Inactive*

(2) Change the startup type for Hitachi Storage Command Suite-related services.
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.
# Hitachi Storage Command Suite related service

12 PFM - Correlator
(3) Reboot the OS
a) Reboot the OS.
3-b.5.2.3 Performing the preprocessing for uninstalling components

(1) Check the directory that stores the database for Hitachi Storage Command Suite Common
Component.

# File Name
1 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.
# Directory
If the hcmdsweb2 command does not exist, go to step (3) in section 3-b.5.2.3.
# Command
1 hcmdsweb2 /delete /type TuningManager
2 hcmdsweb2 /delete /type PerformanceReporter
If the message KAPM04202-I(the command executed successfully) or KAPM04118-E(the

program is already deleted) is displayed, go to step (3) in section 3-b.5.2.3.
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-b.5.2.3.
If the hcmdscancel command does not exist, go to step (4) in section 3-b.5.2.3.
# Command

# File Name
3-b.5.2.4 Uninstalling the Collection Manager component

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.
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
d) Copy the value of the UninstallString entry of the registry key.
e) Paste the copied value into the command prompt window, and then execute this command
to start the uninstallation.
f) When the uninstallation finishes, go to step (4) in section 3-b.5.2.4.

# File Name

If the file does not exist, go to step (3) in section 3-b.5.2.4.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.2.12.
d) Use the registry editor to make sure that the registry key indicated below exists.
# Registry Key
f) Paste the copied value into the command prompt, add the following option, and then
execute the command. The uninstallation will start.
Note: If the uninstallation terminates successfully, the following dialog box indicating such
is displayed. Click OK to close the dialog box.
Figure 3-b.5.2.4-1: Successful uninstallation termination window
Because no windows are displayed during an uninstallation, no user responses are required.

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.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGT0(The last value is a zero.)
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_0A(The
4
second to last character is a zero.)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_0S(The
5
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PC
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PE
8 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PH
9 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PM
10 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PN
11 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PP
12 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PS
13 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PT
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
14
Application\PFM
15
Application\PFM-HealthCheck
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
16
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.
# Shared file name

Note: The {vvrrss} part in the file names is a string of alphanumeric characters that indicates
the DLL version number.

3-b.5.2.5 Uninstalling the Tuning Service component
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-b.5.2.5.
# Registry Key
{89331AB6-2E76-4986-9458-54795EF060A0}
d) Paste the copied value into the command prompt window, and then execute this command
(2) Make sure that Tuning Service has been uninstalled.
# Registry Key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
1
HiCommandTuningService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\
2
HTM-Tuning Service
3
{89331AB6-2E76-4986-9458-54795EF060A0}
3-b.5.2.6 Uninstalling the Performance Reporter component

# Registry Key

{465EF71F-B608-4C33-9E19-D56DDCADC82A}
with the option shown below to start the uninstallation.
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
(2) Make sure that the registry keys indicated below do not exist.
# Registry Key
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
{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 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.

# File
Hitachi Storage
1
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.
# Command line
1 HBuninst /X
d) After the dialog box that indicates termination of the command appears, check the value
that was output to the following file.
# File
1 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.
# Registry Key
(When x86 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\HiCommand Base
1 (When x64 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\
HiCommand Base
(When x86 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\
HiRDBEmbeddedEdition_HD0
2
(When x64 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\
3
HBaseStgMgmtComService
4
HBaseStgMgmtWebService
5
HBaseStorageMgmtWebSSOService

6
HiRDBClusterService_HD0
7
8
Application\HBase Storage Mgmt Log
9
Application\HiRDBEmbeddedEdition_HD0
10
Application\HitachiWebServer
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.
# Directory
1 %temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
3-b.5.2.8 Deleting the database files

If the files do not exist, go to step (2) in section 3-b.5.2.8.
# File name
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
1 db_areapath1
2 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-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 Deleting directories and registry keys

a) Make sure that the directories indicated below do not exist. If these directories exist, delete
them manually.
# Directory

2
{89331AB6-2E76-4986-9458-54795EF060A0}

3
{639938A4-41F1-4643-B5E9-05B1CAC6DA21}

4
{465EF71F-B608-4C33-9E19-D56DDCADC82A}

5
{1345FCD1-713E-4449-8F76-3F6503941040}

6
{61577C30-8F2D-445E-9E9F-54F65EE419A5}

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

2
HiCommandTuningManager
3
Application\TuningManager
4
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
5
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
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
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}
35 {465EF71F-B608-4C33-9E19-D56DDCADC82A}
36 {1345FCD1-713E-4449-8F76-3F6503941040}
37 {61577C30-8F2D-445E-9E9F-54F65EE419A5}
38 {7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
39 {ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
b) Restart the OS.
3-b.5.2.11 Deleting HiCommand Device Manager authentication information

The procedure described in this section applies only when the instance of Tuning Manager server
you forcibly deleted was connected to an instance of HiCommand Device Manager on a remote
host. This procedure must be performed on the remote host.
Perform this procedure only after making sure that no Hitachi Storage Command Suite family of
products other than the forcibly deleted instance of Tuning Manager server have been specified as
connection destinations for the target instance of HiCommand Device Manager.
1. 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.
# Directory
2. Execute the command indicated below.
If the hcmdsintg command does not exist, go to section 3-b.5.2.12.
# Command line
hcmdsintg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ" (
1
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
Product Name :
DeviceManager
ProvisioningManager
TuningManager
# Command line
hcmdsintg /delete /type TuningManager /user "htnmrepuser" /pass
1

d) Execute the command indicated below. Make sure that TuningManager is not included in
the output results.
# Command line
hcmdsintg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ" (
1
3-b.5.2.12 Installation and uninstallation of Tuning Manager server

The procedure of forcibly delete Tuning Manager server is completed in section
3-b.5.2.11. However, if any of the following conditions are met, the additional procedure
described in this section must be performed.
The file does not exist in step (2) b) of section 3-b.5.2.4.
The uninstallation of Collection Manager fails in (2) g) of section 3-b.5.2.4.
might remain. Therefore, perform the following procedures sequentially to delete
the information of Tuning Manager server completely.
3-c Uninstall of the Tuning Manager server for Solaris(Ver.5.1 to Ver.5.9)

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
3-d.2 Applicable Versions

Tuning Manager server for Solaris 6.0.0-00 to earlier than 8
3-d.3 Overview of deleting Tuning Manager server

Figure 3-d.3-1 shows an overview of the process for deleting Tuning Manager server.

START
Normal uninstallation procedure
Do you want to perform an

No
uninstallation that leaves
Agents?
Yes Stopping services. Forcibly Deleting

Deleting Tuning Manager server but
Leaving Agents Preparing for deletion.
Executing the tool for deleting

Common Component and
Was the HiRDB.
uninstallation
No
successful?
Is the No
Yes /tmp/hcmdsrtn.enf
value 0?
Deleting the OS settings
END Yes
Restarting the OS
Forcibly stopping the HiRDB process
Deleting database files
Deleting packages
Deleting files and directories
Restarting the OS
Deleting the HiCommand Device

Manager authentication information.
END
Figure 3-d.3-1 The flow of the deletion of the Tuning Manager server

Notes:
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,
- Only perform the forced deletion procedure described in section 3-d.5 if you cannot perform a
For details about how to uninstall a HiCommand product, see the maintenance manual or other
manuals for the product.
for the products.
3-d.4 Deleting Tuning Manager server without deleting Agent


# Environment variable name Value to specify
1 $CM_NOUNINST 1
(2) Uninstalling Tuning Manager server

Uninstall Tuning Manager server.
When Tuning Manager server is uninstalled successfully, messages indicating the uninstallation
results are output to log files in the /var/opt/HiCommand/logs directory.
# File name Output results Explanation
1 HTM_UNINST_LOG_{ 20080521 - 20:28:10 (localtime) Tuning Manager server
MM-DD-YYYY_hh_m Tuning Manager server was successfully uninstallation log
m_ss}.trc uninstalled.
2 HTMPR_UNINST_LO 20080521 - 20:26:56 (localtime) HTM - Performance

G_{MM-DD-YYYY_h Performance Reporter uninstall success. Reporter uninstallation
h_mm_ss}.trc log

1 $CM_NOUNINST
Note: If an error occurs during the deletion procedure in 3-d.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-d.5.
3-d.5 Forcibly Deleting Tuning Manager server

3-d.5.1 Stopping Services
Perform the following procedure to stop services.
(1) Execute the commands indicated below to stop the Hitachi Storage Command Suite-related
services.
If these commands do not exist, go to section 3-d.5.2.
(2) Execute the following command and make sure that all the services indicated in the output
results have stopped.
# Command
1 ./hcmdssrv status
Output results
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 Preparing for Deletion

(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
1 /opt/HiCommand/Base/conf/hcmdsdbinit.ini initpath

(2) Copy the file indicated below to a valid directory.
If this file does not exist, go to section 3-d.5.4.
# File to copy
1 /var/opt/HiCommand/Base/tmp/HBuninst.sh
# Directories to which you must not copy the file

1 /opt/HiCommand (including subdirectories)
2 /opt/jp1pc (including subdirectories)
3 /var/opt/HiCommand (including subdirectories)

4 /tmp (including subdirectories)
3-d.5.3 Executing the Tool for Deleting Common Component and HiRDB
(1) Execute the commands indicated below.
If these commands do not exist, go to step (2).
# Command
1 cd /opt/HiCommand/Base/bin/
2 ./hcmdscancel PerformanceReporter
3 ./hcmdscancel TuningManager

Use the following commands to execute the HBuninst.sh command you copied in step (2) of
section 3-d.5.2.
# Command
1 cd <directory-to-which-HBuninst.sh-has-been-copied>
2 ./HBuninst.sh /X
Note: /X is an option, not a directory.
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:
(3) Check the value specified in the following file.

# File
1 /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-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 Deleting the OS Settings

(1) Delete the settings related to Common Component.
Delete the following files.
# File
1 Files in /etc/init.d whose names begin with hicommand-
2 Files in /etc/rc2.d whose names begin with K99hicommand-
3 Files in /etc/rc3.d whose names begin with S99hicommand-
4 Files in /etc/rc3.d whose names begin with I99hicommand-
5 /etc/init.d/HiRDB_E.opt.HiCommand.Base.HDB
6 /etc/rc0.d/K090HiRDB_E.opt.HiCommand.Base.HDB
7 /etc/rc1.d/K090HiRDB_E.opt.HiCommand.Base.HDB
8 /etc/rc2.d/S91HiRDB_E.opt.HiCommand.Base.HDB
9 /etc/rc3.d/S91HiRDB_E.opt.HiCommand.Base.HDB
(2) Delete the HiRDB-related settings.

Delete the following entries that were added to /etc/inittab.
Entries to delete
pe01: < number >:wait:/opt/HiCommand/Base/HDB/etc/pdpwon_e
pd01:< number >:respawn:env LD_LIBRARY_PATH=/opt/HiCommand/Base/HDB/lib
/opt/HiCommand/ Base/HDB/lib/servers/pdprcd /opt/HiCommand/Base/HDB
3-d.5.5 Restarting the OS

Restart the OS.

3-d.5.6 Forcibly Stopping the HiRDB Process
(1) Specify the following environment variables.
The method for specifying these environment variables differs depending on the shell you are
using.
# Environment Value
variable name
# Shell Example of setting an environment variable

export PDDIR
export PDCONFPATH
3 csh/tcsh setenv PDDIR /opt/HiCommand/Base/HDB
4 Other shells See the documentation for your shell.
(2) Execute the command indicated below.

If the command does not exist, go to step (3).
# Command
1 /opt/HiCommand/Base/HDB/bin/pdstop f
(3) Execute the following command to confirm that a pdprcd process is running.
# Command
1 ps ef |grep pdprcd
(4) If the /opt/HiCommand/Base/HDB/lib/servers/pdprcd process exists in the system, forcibly stop

the process.
# Command
1 kill 9 <pdprcd-process-number>
Note: You can use the ps command to check the process number (PID) of pdprcd.

3-d.5.7 Deleting Database Files
(1) Delete the Tuning Manager database files.
(a) Open the following files. If there are no such files, proceed to (2). Note that these files
might not be created.
# File Name
1 /opt/HiCommand/TuningManager/inst/db_area.properties
2 /opt/HiCommand/TuningManager/inst/db_area_6.properties
(b) In these files, check the values of the properties indicated below, which indicate the
file.
# File Name
1 db_areapath1
2 db_areapath2
(c) Delete the directories indicated by the properties db_areapath1 and db_areapath2. If there
are no such directories, proceed to (2).
(2) Delete the database files for Common Component.

Delete the directory whose name you wrote down in step (1) of section 3-d.5.2.
If there was no file in step (1) of section 3-d.5.1, go to section 3-d.5.8.
3-d.5.8 Deleting Packages

(1) Delete the HTMCD1 package.
Use the following command to delete the package.
# Command
1 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
1 /var/sadm/pkg/HTMCD1
(2) Delete the HTMCD2 package.

# Command
1 pkgrm HTMCD2
# Directory
1 /var/sadm/pkg/HTMCD2
(3) Delete the HTMClmgr package.

# Command
1 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
1 /var/sadm/pkg/HTMClmgr
# Files
1 /etc/init.d/jp1_pc
2 /etc/rc0.d/K01_JP1_10_PC
3 /etc/rc2.d/S99_JP1_90_PC
(4) Delete the HTMClmgr package.

Delete the HTMPR package.
# Command
1 pkgrm HTMPR
# Directory
1 /var/sadm/pkg/HTMPR
(5) Delete the HTMTsvc package.

# Command
1 pkgrm HTMTsvc
# Directory
1 /var/sadm/pkg/HTMTsvc

(6) Delete the HBASE package.
Note: You do not need to perform this step if the final value of /tmp/hcmdsrtn.enf was 0 in step (3)
of section 3-d.5.3.
# Command
1 pkgrm HBASE
# Directory
1 /var/sadm/pkg/HBASE
3-d.5.9 Deleting Files and Directories

Delete the following directories.
# Directory
1 /opt/HiCommand
2 /var/opt/HiCommand
3 /opt/jp1pc
Delete the following entries from etc/services.

Entry to delete
jp1pcnsvr 22285/tcp # Performance Management Name Server
jp1pcstatsvr 22350/tcp # Performance Management Status Server
jp1pcvsvr 22286/tcp # Performance Management View Server
jp1pcovsvr 22292/tcp # Performance Management NNM Object Manager
Execute the following commands to delete installed information, and then terminate the
commands.
# Command
1 /etc/hitachi_setup
2 /etc/hitachi_x64setup
# Installed information item (displayed in the PP-NAME column) to delete

1 JP1/PFM - Manager
Use the following command to check the number of products that have been installed.
# Command
1 /etc/.hitachi/bin/SHOWPP

If the command displays TOTAL: 0 products, delete the following directory and files.
# Directory
1 /etc/.hitachi
# Files
1 /etc/hitachi_start
3 /etc/hitachi_x64setup
3-d.5.10 Restarting the OS

Restart the OS.
3-d.5.11 Deleting the HiCommand Device Manager authentication information.


If this directory does not exist, the procedure ends.
# Directory
1 /opt/HiCommand/Base/bin

If the hcmdsintg command does not exist, the procedure ends.
# Command line
1 hcmdsintg -print -user "htnmrepuser" -pass " INTERNAL HRXJIHVZ"
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
Product Name :
DeviceManager
ProvisioningManager
TuningManager

# Command line
hcmdsintg -delete -type TuningManager -user "htnmrepuser" -pass " INTERNAL
1
HRXJIHVZ"
the output results.
# Command line
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
1 RAID Agent 6.0.0-00 to earlier than 8.0.0-00 Windows
2 Agent for Server System 6.0.0-00 to earlier than 8.0.0-00 Windows
3 Switch Agent 6.0.0-00 to earlier than 8.0.0-00 Windows
4 NAS Agent 6.0.0-00 to earlier than 8.0.0-00 Windows
5 Oracle Agent 6.0.0-00 to earlier than 8.0.0-00 Windows
6 SQL Agent 6.0.0-00 to earlier than 8.0.0-00 Windows
[Note1] Only for HDS version.
[Note2] In this document, the procedure for how to delete the agent information, which is
required for enabling us to re-install the agent, is described, that is, some of the agent
information is still remained which does not affect the re-install of the agents.
3-e.3 Notes for the operation
(1) If you delete the agent information by the procedure described in the chapter 3-e, all the
programs of Hitachi Tuning Manager installed on the same server should be deleted. You cannot
delete the target program of Hitachi Tuning Manager only.
(2) Some of the agent information will still remain on the host even if you did the force deletion
procedure described in the chapter 3-e. so make sure that you re-install the agents which were
installed on the server after you force delete the agent information so that agent installation
environment will be recovered systematically. After that, uninstall the agent or setup the agent
instance environment normally, if required.
(3) If Tuning Manager server is installed on the same server where the agent is installed, delete the
agent information first by following the procedure described in the chapter 3-e, After that, to
delete the Tuning Manager server information, perform the procedure in 3-b if the Tuning
Manager server version is 6.0 to earlier than 8.0.

3-e.4 The flow of the force deletion and re-install the agent
Figure 3-e.4-1 shows the flow of the deletion of the agent and the flow of re-install the agent.
Start
Uninstall the agent by the uninstaller
The procedure of force deletion

Uninstaller No of the agent
Normally End
Yes
Stop the agent related service
Reboot the OS
Delete the file/directory
Both conditions
No
in (*1) met?
Yes
Use the htnmagtregclean Manually delete the registry

command to delete the registry key
Reboot the OS
(*1) : The htnmagtregclean command (version 1.0.0) can only be used if

both of the following conditions are met:
(a) Windows Server 2003 (x86/x64/IPF) or Windows Server 2008
Install the Agent (x86/x64/IPF) is being used.
(b) Every Agent instance version is from 6.0.0-00 to earlier than
8.0.0-00.
End
Figure 3-e.4-1 The flow of the deletion of the agent and re-install the agent

3-e.5 Uninstall by the uninstaller
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 Force deletion of the agent

3-e.6.1 Stop the agent related service
(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.

# Agent related service
7 PFM - Correlator
14 PFM - Agent for xxxx yyyy
15 PFM - Agent Store for xxxx yyyy
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 Type of the agent Single or Multi Instance
1 RAID Agent RAID Multi Instance
2 Agent for Server System *1 RAID Map Single Instance
Windows Single Instance
MSExchange Single Instance
3 Switch Agent SANSwitch Multi Instance
4 NAS Agent NAS Multi Instance
5 Oracle Agent Oracle Multi Instance
6 SQL Agent Microsoft(R) SQL Server Multi Instance
[*1] Agent for Server System consists of 3 agents, RAID Map/Windows/Exchange agent.
(2) Reboot the OS

Reboot the OS so that the agent related service should stop.
3-e.6.2 Delete the file/directory

(1) Get the information of the installation directory of the agent
(a) Open the registry editor by executing the regedit command.
(b) Check whether following registry key exists or nor in registry editor. If the registry key does
not exist, go to the chapter 3-e.6.3
<Windows (x86) or Windows (IPF)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC\PathName
<Windows (x64)>
# Registry Key
1 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.
(2) Delete the agent installation directory

(a) Open the command prompt and execute the following OS command.
Specify the directory path got in the chapter 3-e.6.2 (1) as the <Agent Installation
Directory>.

# Command
1 rd /S /Q <Agent Installation Directory>
3-e.6.3 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
1 Windows Server 2003 x86 Including R2.
3 Windows Server 2003 IPF -
4 Windows Server 2008 x86 -
6 Windows Server 2008 IPF -
# Agent Version
1 RAID Agent 6.0.0-00 to earlier than 8.0.0-00
2 Agent for Server System 6.0.0-00 to earlier than 8.0.0-00
3 Switch Agent 6.0.0-00 to earlier than 8.0.0-00
4 NAS Agent 6.0.0-00 to earlier than 8.0.0-00
5 Oracle Agent 6.0.0-00 to earlier than 8.0.0-00
6 SQL Agent 6.0.0-00 to earlier than 8.0.0-00
The following are notes on using the htnmagtregclean command.

# Notes
1 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.
2 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.
3 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 (n : Total number of agent instances)
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.
5 After you execute the htnmagtregclean command, delete the log file.
6 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.

The htnmagtregclean command can be used to delete the following registry keys:
# Registry Key
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
(*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
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.
(2) Execute the htnmagtregclean command.
# Command
1 htnmagtregclean
(3) The following message appears in the command prompt.

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

0 Normal termination code
1 Warning termination code. (One or more registries were not deleted.)
(a) An end code value of 1
Information regarding the fact that registry keys could not be deleted is recorded in the log
file. Check the log file. This file is located directly under the system drive.
# Log File
1 %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 Action
1 A user without administrator Log in as a user that belongs to the Administrators
privileges attempted to execute the group, and then re-execute the htnmagtregclean
htnmagtregclean command. command.
2 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
for Delete Permission. permission settings of the registry key.
3 A registry key has been locked. Using the service control manager, specify Manual
as the Startup type for agent-related services.
Reboot 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 that has administrator start an elevated command prompt that has
privileges to execute the administrator privileges. Use the elevated command
htnmagtregclean command. prompt to re-execute the htnmagtregclean command.
(5) After using the htnmagtregclean command to delete the registry keys, delete the log file.

# Log File
Below is the format of log data output.
< Format >
Date Time Loglevel Message

Loglevel:
(I) : Information
(W) : Warning
(E) : Error
<Message displayed if a registry key is successfully deleted>

Wed 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:
<Message displayed if an attempt to delete a registry key fails>

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:

3-e.6.4 Delete the registry key (Manually deleting the registry keys)
(1) Check whether following registry keys exist or nor by using registry editor, and if exist, delete
them by manually.
# Registry Key
instance name.
<Windows (x64)>
# Registry Key
instance name.
3-e.6.5 Reboot the OS

Reboot the OS.

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
1 RAID Agent 6.0.0-00 to 7.0 *1 Solaris (SPARC)/Solaris (x64)/HP-UX/AIX
7.1.0-00 to earlier Solaris (SPARC)/Solaris (x64)/
than 8.0.0-00 HP-UX/AIX/Linux
2 Agent for Server System 6.0.0-00 to earlier Solaris (SPARC)/Solaris (x64)/HP-UX/AIX/Linux
than 8.0.0-00
3 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 Solaris (SPARC)/Solaris (x64)
7.1.0-00 to earlier Solaris (SPARC)/Solaris (x64)/Linux
than 8.0.0-00
4 NAS Agent 6.0.0-00 to 6.2 *1 Solaris (SPARC)/HP-UX/AIX
6.3.0-00 to earlier Solaris (SPARC)
than 8.0.0-00
5 Oracle Agent 6.0.0-00 to earlier Solaris (SPARC)/Solaris (x64)/HP-UX/AIX/Linux
than 8.0.0-00
6 DB2 Agent 6.0.0-00 to earlier AIX/Linux
than 8.0.0-00
7 EAP Agent 7.1.1-00 to earlier Solaris(SPARC), HP-UX
than 8.0.0-00
(*1) Including its bug fix version

3-f.3 Notes for the operation
(1) If you delete the agent information by the procedure described in the chapter 3-f, all the programs
of Hitachi Tuning Manager installed on the same server should be deleted. You cannot delete the
target program of Hitachi Tuning Manager only.
procedure described in the chapter 3-f. so make sure that you re-install the agents which were
agent information first by following the procedure described in the chapter 3-f. After that, to
delete the Tuning Manager server information, perform the procedure in 3-d if the Tuning
Manager server for Solaris version is from 6.0 to earlier than 8.0, or perform the procedure in 3-g
if the Tuning Manager server for Linux version is from 7.1 to earlier than 8.0.
3-f.4 The flow of the force deletion and re-install the agent
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 The procedure of force deletion
Normally End of the agent
Yes
Reboot the OS
Install the Agent
End
Figure 3-f.4-1 The flow of the deletion of the agent and re-install the agent

3-f.5 Uninstall by the uninstaller
Uninstall the agent by following with the procedure described in the following manual:
- In Ver.6
- In Ver.7
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 Force deletion of the agent

3-f.6.1 Stop the agent related service
(1) Stop the services of Tuning Manager Agents
(a) Execute the following command in the console.
# Command
1 cd /opt/jp1pc/tools
2 ./jpcstop all
(2) Change the setting of the service automatically started

(a) Execute the following OS command in the console.
# Command
1 rm -rf /opt/jp1pc/jpc_start
For AIX:
rmitab jp1pc
2
For SUSE Linux:
chkconfig jp1_pc off
(3) Reboot the OS

Reboot the OS.

(4) Stop the service of Tuning Manager server
In UNIX, if Tuning Manager server is also installed into the server where the agent is
installed, stop the service of Tuning Manager server.
# Command
1 For Solaris:
cd /opt/HiCommand/Base/bin
For Linux:
cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
2 ./hcmdssrv -stop
3-f.6.2 Delete the file/directory

If these files do not exist, go to section 3-f.6.2(3).
(a) Solaris
# File
(b) Linux
# File
(2) Delete the installation directory of the agent

# Command
1 rm -rf /opt/jp1pc
3-f.6.3 Reboot the OS

Reboot the OS.

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):
3-g.2 Applicable Versions

Tuning Manager server for Linux 7.1.0-00 to earlier than 8.0.0-00
3-g.3 Overview of deleting Tuning Manager server

Figure 3-g.3-1 shows an overview of the process for deleting Tuning Manager server.

START

No
Agents?
Yes Stopping services. Forcibly Deleting


Was the HiRDB.
uninstallation
No
successful?
Is the No
Yes /tmp/hcmdsrtn.enf
value 0?
END Yes
Restarting the OS
Deleting packages
Restarting the OS

END
Figure 3-g.3-1 The flow of the deletion of the Tuning Manager server

Notes:
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,
- Only perform the forced deletion procedure described in section 3-g.5 if you cannot perform a
For details about how to uninstall a HiCommand product, see the maintenance manual or other
manuals for the product.
for the products.
3-g.4 Deleting Tuning Manager server without deleting Agent


1 $CM_NOUNINST 1

results are output to log files in the /var<TuningManager-Installation-directory>/logs directory.



h_mm_ss}.trc log

1 $CM_NOUNINST
Note: If an error occurs during the deletion procedure in 3-g.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-g.5.
Note: This note applies when you install a Hitachi Command Suite products after deleting Tuning
Manager server as described in 3-g.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.
3-g.5 Forcibly Deleting Tuning Manager server

3-g.5.1 Stopping Services
(1) Execute the commands indicated below to stop the Hitachi Storage Command Suite-related
services.
If these commands do not exist, go to section 3-g.5.2.
# Command
1 ./hcmdssrv status
Output results
have not stopped, go to section 3-g.5.2.

3-g.5.2 Preparing for Deletion
If this file does not exist, go to step (2).
# File name Property
name
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>/conf/hcmdsdbinit.ini initpath
(2) Copy the file indicated below to a valid directory.

If this file does not exist, go to section 3-g.5.4.
# File to copy
1 /var<Hitachi-Command-Suite-Common-Component-Installation-directory>/tmp/HBuninst.sh
# Directories to which you must not copy the file
1 <TuningManager-Installation-directory> (including subdirectories)
2 <Hitachi-Command-Suite-Common-Component-Installation-directory> (including
subdirectories)
3 /opt/jp1pc (including subdirectories)
4 /var<TuningManager-Installation-directory> (including subdirectories)
5 /var<Hitachi-Command-Suite-Common-Component-Installation-directory> (including
subdirectories)
6 /tmp (including subdirectories)
3-g.5.3 Executing the Tool for Deleting Common Component and HiRDB
If these commands do not exist, go to step (2).
# Command
1 cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin/

Use the following commands to execute the HBuninst.sh command you copied in step (2) of
section 3-g.5.2.
# Command
2 ./HBuninst.sh /X
Note: /X is an option, not a directory.


Output result 1
Output result 2
(3) Check the value specified in the following file.

# File
1 /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 Deleting the OS Settings

# File
8 /etc/init.d/HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
9 /etc/rc0.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
15 /etc/init/2248.PDnn.conf (Only RHEL 6.x)
16 /etc/init/2248.penn.conf (Only RHEL 6.x)
nn:double digit numbers

NOTE:
If Hitachi Storage Command Suite Common Component is installed in the default location,
<Base-installation-directory> is replaced with "opt.HiCommand.Base".
If Hitachi Storage 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 ".".

Delete the following entries that were added to /etc/inittab.
Entries to delete
pe01: < number
>:wait:<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/etc/pdpwon_e
PD01: < number
>:respawn:<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdd
3-g.5.5 Restarting the OS

Restart the OS.
3-g.5.6 Forcibly Stopping the HiRDB Process

using.
# Environment Value
variable name
1 PDDIR <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
2 PDCONFPATH <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/conf
3 LD_LIBRARY_PATH <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib

1 bash source <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/
pduxenv
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
3 csh/tcsh setenv PDDIR <Hitachi-Command-Suite-Common-Component-Installation-directory>/
HDB
setenv PDCONFPATH <Hitachi-Command-Suite-Common-Component-Installation-dire
ctory>/HDB/conf
setenv LD_LIBRARY_PATH <Hitachi-Command-Suite-Common-Component-Installati
on-directory>/HDB/lib

# Command
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdstop f
# Command
(4) If the <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib/servers/pdprcd
process exists in the system, forcibly stop the process.

# Command
3-g.5.7 Deleting Database Files

# File Name
1 <TuningManager-Installation-directory>/inst/db_area.properties

2 <TuningManager-Installation-directory>/inst/db_area_6.properties
file.
# File Name
1 db_areapath1
2 db_areapath2

Delete the directory whose name you wrote down in step (1) of section 3-g.5.2.
If there was no file in step (1) of section 3-g.5.2, go to section 3-g.5.8.
3-g.5.8 Deleting Packages

(1) Delete the HTNM package.
# Command
1 rpm -e HTNM
(2) Delete the HTMPR package.

# Command
1 rpm e HTMPR
3-g.5.9 Deleting Files and Directories

Delete the following directories.
# Directory
5 /opt/jp1pc
6 /etc/.hitachi/HBase
7 /etc/.hitachi/HTNM
Delete the following entries from /etc/services.

Entry to delete
commands.
# Command

1 JP1/PFM - Manager
# Command
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
1 /etc/.hitachi
# Files
3-g.5.10 Restarting the OS

Restart the OS.
3-g.5.11 Deleting the HiCommand Device Manager authentication information.


# Directory
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin

If the hcmdsintg command does not exist, the procedure ends.
# Command line
Output example
Product Name :
DeviceManager
ProvisioningManager
TuningManager

# Command line
hcmdsintg -delete -type TuningManager -user "htnmrepuser" -pass " INTERNAL
1
HRXJIHVZ"
the output results.
# Command line

3-h Deleting Tuning Manager server for Windows (Ver.8 or later)
3-h.1 Purpose
This appendix provides an overview of deleting Tuning Manager server for Windows, and describes
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

Tuning Manager server for Windows 8.0.0-00 or later
3-h.3 Overview of deleting Tuning Manager server

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 Stopping services related to Tuning Manager server

an uninstallation that leaves NO
Agents?
YES
Performing the preprocessing for uninstalling components
Uninstall the Tuning Manager server The agents must also be
without uninstalling Agents
uninstalled
Uninstalling the Collection Manager component
NO
Was the uninstallation successful?
Uninstalling the Performance Reporter component
YES
Normal uninstallation procedure Uninstall the Hitachi Storage Command Suite common component
NO
Was the uninstallation Deleting the database files
successful?
YES
YES
Deleting directories and registry keys
Can the user fix the error?

Restarting the OS
NO
End
Delete HiCommand Device Manager authentication information
End
End

Figure 3-h.3-1 The flow of the deletion of the Tuning Manager server
Notes:
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
- 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.
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 Deleting Tuning Manager server without deleting Agent

1 CM_NOUNINST 1
(2) Uninstalling Tuning Manager server.
Uninstall Tuning Manager server. When Tuning Manager server is successfully uninstalled, the
following window appears.
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 CM_NOUNINST
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 Forcibly Deleting Tuning Manager server

If there is a registry deletion command (htnmsvrregclean.bat) that is supported by Tuning
Manager server, follow the procedure described in 3-h.5.1. If there is no command, follow the
procedure described in 3-h.5.2 to forcibly delete Tuning Manager server manually.
# Tuning Manager server version Registry deletion command version

1 In 8.0.0 or later 2.0.0-00
Notes:

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.
1. About execution of Hitachi Command Suite Common Component commands

Part of the description of Hitachi Command Suite Common Component requires replacement. The
part to be replaced and how to replace it are shown below. Note that all output examples shown
here are for the new version (version 8 or later).
Also note that if the installation directory for the old version (version 7 or earlier) of Hitachi
Command Suite Common Component does not exist, you do not need to perform the operations
described here. This is because the old version (version 7 or earlier) of Hitachi Command Suite
Common Component has already been uninstalled.
-Hitachi Command Suite Common Component installation directory

Relevant text: %SystemDrive%\Program Files\HiCommand\Base64\bin
Replace the above text with the following text:
%SystemDrive%\Program Files\HiCommand\Base\bin (in an x86 environment)
%SystemDrive%\Program Files (x86)\HiCommand\Base\bin (in an x64 environment)
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.
- Names of Hitachi Command Suite Common Component commands
Relevant text: hcmds64xxx

Replace the above text with the following text: hcmdsxxx
Command names that do not begin with hcmds64 do not need to be replaced. However, the
location of these commands was changed from bin to sbin, as shown below:
Relevant text: %SystemDrive%\Program Files\HiCommand\Base64\sbin\hcmds***
Replace the above text with the following text: %SystemDrive%\Program
Files\HiCommand\Base\bin\hcmds***

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 Procedure for using the registry deletion command
3-h.5.1.1 Terms
# Terms Directory
Hitachi Command %SystemDrive%\Program Files\HiCommand\Base64
1 Suite-Common-Component-installation-d
irectory
Hitachi-Tuning-Manager-installation-dire %SystemDrive%\Program Files \HiCommand\TuningManager

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 Stopping services related to Tuning Manager server

In an environment in which an upgrade from version 7 or earlier has been performed, you also
need to perform steps a) to c) shown below in the old environment (version 7 or earlier). When
you do so, follow the text-replacement instructions described above.

If the directory does not exist, go to step (1) d) in section 3-h.5.1.2.
# Directory
1 Hitachi Command Suite-Common-Component-installation-directory\bin
If the hcmds64srv command does not exist, go to step (1) d) in section 3-h.5.1.2.
# Command
1 hcmds64srv /stop
# Command
1 hcmds64srv /status
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
KAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt SSO Service
KAPM05009-I Already stopped service. service-name=HCS TuningManager REST Application Service
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.
If the directory does not exist, go to step (2) in section 3-h.5.1.2.
# Directory
1 Collection-Manager-installation-directory\jp1pc\tools
If the jpcstop command does not exist, go to step (1) f) in section 3-h.5.1.2.
# Command

1 jpcstop all
Output example
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)
If the jpcctrl command does not exist, go to step (2) in section 3-h.5.1.2.
go to step (2) in section 3-h.5.1.2.
# Command
1 jpcctrl list *
--------- --------- ------------- -------- -------- --------
XXXX PH1XXX Action Handler Inactive*)
XXXX OS1XXX Agnet Store Inactive*
XXXX OA1XXX Agent Collector Inactive*
(2) Change the startup type for Hitachi Command Suite-related services.

b) Change the startup type to Manual for all of the following Hitachi 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-h.4, some services might not be
displayed.
# Hitachi Command Suite related service

1 HBase 64 Storage Mgmt Web Service
2 HBase 64 Storage Mgmt Web SSO Service
3 HBase 64 Storage Mgmt SSO Service
6 HCS TuningManager REST Application Service
12 PFM View Server
13 PFM Trap Generator
14 PFM Correlator
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.
# Hitachi Command Suite related service(version 7 or earlier)


(3) Reboot the OS
a) Reboot the OS.
3-h.5.1.3 Performing the preprocessing for uninstalling components

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.
If the file does not exist, go to step (2) in section 3-h.5.1.3.
# File Name
1 Hitachi Command Suite-Common-Component-installation-directory\conf\hcmdsdbinit.ini
file.
# Directory
If the hcmdsweb command does not exist, go to step (3) in section 3-h.5.1.3.
# Command
1 hcmdsweb /delete /type TuningManager
2 hcmdsweb /delete /type PerformanceReporter
If the message KAPM04692-I (the command executed successfully) or KAPM04118-E

(Program type is not registered.) is displayed, go to step (3) in section 3-h.5.1.3.
section 3-h.5.1.3.
If the hcmdscancel command does not exist, go to step (4) in section 3-h.5.1.3.
# Command
(4) Delete the file.
If the file does not exist, go to section 3-h.5.1.4.
# File Name
3-h.5.1.4 Uninstalling the Collection Manager component
(1) Execute the Collection Manager uninstaller .


# File Name
If the file does not exist, go to section 3-h.5.1.5. If the file does not exist, some of the
Manager server, perform the procedure described in section 3-h.5.1.12.

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.

If neither registry key exists, go to section 3-h.5.1.5.
# Registry Key
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersio
n\Uninstall\<Collection Manager-GUID>

Figure 3-h.5.1.4-1: Successful uninstallation termination window
g) After executing the uninstaller, go to section 3-h.5.1.5.
procedure described in section 3-h.5.1.12.
3-h.5.1.5 Uninstalling the Tuning Service component

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.
If this key does not exist, go to section 3-h.5.1.6.
# Registry Key
{89331AB6-2E76-4986-9458-54795EF060A0}

3-h.5.1.6 Uninstalling the Performance Reporter component

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 information in a version-7 environment:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{465EF71F-B608-4
C33-9E19-D56DDCADC82A}
If this registry key does not exist, go to section 3-h.5.1.7.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninst
all\{465EF71F-B608-4C33-9E19-D56DDCADC82A}
values.
# File Name
3-h.5.1.7 Uninstalling the Hitachi Command Suite Common Component

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.
In an environment that satisfies any of the above conditions:

You must forcibly delete both the 32-bit and 64-bit versions of Hitachi Command Suite Common
Component. Go to step (1) to forcibly delete them.
In an environment that does not satisfy any of the above conditions:

You must forcibly delete the 64-bit version of Hitachi Command Suite Common Component. Go
to step (2) to forcibly delete it.
(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
1 %SystemDrive%\Program Files (x86)\HiCommand\Base\tmp\HBuninst.exe
Note:
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.
# Command line
1 HBuninst /X
d) After the dialog box that indicates termination of the command appears, check the
value that was output to the following file.
# File
1 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).
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
1
Ver.8.1 or later
%SystemDrive%\Program Files\HiCommand\Base64\tmp\HB64uninst.exe
Note:
# Command line
HBuninst /X
1
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.
# File
1 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 Executing the registry deletion command

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,
the command might not operate correctly.
In this case, use an elevated command prompt to execute the command. To start an elevated
command prompt, right-click the command prompt icon, and then choose Run as
administrator from the context menu.
- Do not execute programs (such as installers or registry editors) that access the registry.
- Do not attempt to start the registry deletion command again if it already has been started.
- During execution, do not cancel the registry deletion command by Windows operations such
- Only execute the registry deletion command when there is at least 100 KB of available space
(required for the log file) on the system drive. If the log file already exists, confirm that the file
is write-enabled, and then execute the command.
- Note that the htm-getlogs command does not collect the log file that is generated when the
registry deletion command is executed.
- The log file is not automatically deleted. If the file is no longer needed, perform the forced
uninstallation procedure, and then manually delete the file.
(2) Open a command prompt.

(3) Execute the registry deletion command (htnmsvrregclean.bat). You will be asked if you want to
continue. Enter y.
Removal of the registry keys for HTnM Server will now start.
(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.
Press the Enter key to terminate the htnmsvrregclean.bat. command.

- If the end code is 0, go to section 3-h.5.1.9.
- If the end code is not 0, go to step (5) in section 3-h.5.1.8.
(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
1 %SystemDrive%\htnmsvrregclean.log
The possible causes of the errors are described below.

Refer to the end code and then re-execute the command.
If you re-execute the command and the end code is still not 0, open the above file and check
which registry entries could not be deleted. Delete these manually.
# End Error Cause Action

code
1 1 Registry deletion In the access permission settings for Disable the Deny setting in Delete
failed. the registry key, Deny has been Permission of the access permission
specified for Delete Permission. settings for the registry key, and then
re-execute the command.
2 The registry key to be deleted has The registry key to be deleted might be
been locked. locked while an HTnM operation is being
switched over, such as when a service is
being started. Using the service control
manager, specify Manual as the Startup
type for agent-related services. Reboot the
OS, and then re-execute the command.
3 You do not have administrator Right-click command prompt icon, and then
privileges. An unelevated command choose Run as administrator to start an
prompt (one that does not have elevated command prompt. Then, use the
administrator privileges) was used elevated command prompt to re-execute the
to execute the command in . command.
4 You do not have administrator Log in as a user that belongs to the
privileges. This user does not Administrators group, and then re-execute
belong to the Administrators group. the command.
3-h.5.1.9 Reboot the OS

Reboot the OS
3-h.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.
# Shared file name

1 %SystemRoot%\SysWOW64\htmjpccomm.dll

2 %SystemRoot%\SysWOW64\jpcaudit{vvrrss}.dll
3 %SystemRoot%\SysWOW64\jpccomm{vvrrss}.dll
4 %SystemRoot%\SysWOW64\jpccommhcc.dll
5 %SystemRoot%\SysWOW64\jpccoommhccjp.dll
6 %SystemRoot%\SysWOW64\jpcodbc.dll
(2) Delete the component install temporary directories that are shared by Hitachi Command Suite.
# Directory
1 %temp%\{1345FCD1-713E-4449-8F76-3F6503941040}

need to perform the steps shown below in the old environment (version 7 or earlier)
If the files do not exist, go to step (4) in section 3-h.5.1.10.
# File name
file.
# Property Name
1 db_areapath1
2 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.
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.
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

2
{89331AB6-2E76-4986-9458-54795EF060A0}

3
{639938A4-41F1-4643-B5E9-05B1CAC6DA21}

4
{465EF71F-B608-4C33-9E19-D56DDCADC82A}

5
{1345FCD1-713E-4449-8F76-3F6503941040}

6
{61577C30-8F2D-445E-9E9F-54F65EE419A5}

7
3-h.5.1.11 Deleting Device Manager authentication information

you forcibly deleted was connected to an instance of Device Manager on a remote host. This
procedure must be performed on the remote host.
Perform this procedure only after making sure that no Hitachi Command Suite family (including
Hitachi File Services Manager and Hitachi Storage Navigator Modular 2) of products other than
the forcibly deleted instance of Tuning Manager server have been specified as connection
destinations for the target instance of Device Manager.
(1) Delete the Device Manager authentication information.

If this directory does not exist, go to section 3-h.5.1.12.
# Directory
If the hcmdsintg command does not exist, go to section 3-h.5.1.12.
# Command line
hcmds64intg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ" (
1
to the next step. If TuningManager is not included, go to section 3-h.5.1.12.
Output example
Product Name :
DeviceManager
TuningManager
# Command line
hcmds64intg /delete /type TuningManager /user "htnmrepuser" /pass
1
the output results.
# Command line
1
3-h.5.1.12 Installation and uninstallation of Tuning Manager server

The procedure of forcibly delete Tuning Manager server is completed in section 3-h.5.1.11.
However, if any of the following conditions are met, the additional procedure described in
this section must be performed.
The file does not exist in step (2) b) of section 3-h.5.1.4.
The uninstallation of Collection Manager fails in (2) g) of section 3-h.5.1.4.
might remain. Therefore, perform the following procedures sequentially to delete the
information of Tuning Manager server completely.

3-h.5.2 Procedure for manually deleting registry entries
3-h.5.2.1 Terms
# Terms Directory
Hitachi Command %SystemDrive%\Program Files\HiCommand\Base64
1 Suite-Common-Component-installation-dir
ectory
Hitachi-Tuning-Manager-installation-direct %SystemDrive%\Program Files

2
ory \HiCommand\TuningManager
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.2.2 Stopping services related to Tuning Manager server

need to perform steps a) to c) shown below in the old environment (version 7 or earlier). When
you do so, follow the text-replacement instructions described above.
If the directory does not exist, go to step (1) d) in section 3-h.5.2.2.
# Directory

If the hcmds64srv command does not exist, go to step (1) d) in section 3-h.5.2.2.
# Command
1 hcmds64srv /stop
# Command
1 hcmds64srv /status
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.
# Directory
1 Collection-Manager-installation-directory\jp1pc\tools
If the jpcstop command does not exist, go to step (1) f) in section 3-h.5.2.2.
# Command
1 jpcstop all
Output example
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)
If the jpcctrl command does not exist, go to step (2) in section 3-h.5.2.2.
go to step (2) in section 3-h.5.2.2.
# Command
1 jpcctrl list *
--------- --------- ------------- -------- -------- --------
XXXX PH1XXX Action Handler Inactive*)
XXXX OS1XXX Agnet Store Inactive*
XXXX OA1XXX Agent Collector Inactive*
(2) Change the startup type for Hitachi Command Suite-related services.
b) Change the startup type to Manual for all of the following Hitachi 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-h.4, some services might not be
displayed.

3 HBase 64 Storage Mgmt SSO Service
6 HCS TuningManager REST Application Service
12 PFM View Server
13 PFM Trap Generator
14 PFM Correlator
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.
# Hitachi Command Suite related service(version 7 or earlier)


(3) Reboot the OS
a) Reboot the OS.
3-h.5.2.3 Performing the preprocessing for uninstalling components

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.
If the file does not exist, go to step (2) in section 3-h.5.2.3.
# File Name
1 Hitachi Command Suite-Common-Component-installation-directory\conf\hcmdsdbinit.ini
file.
# Directory
If the hcmdsweb command does not exist, go to step (3) in section 3-h.5.2.3.
# Command
1 hcmdsweb /delete /type TuningManager
2 hcmdsweb /delete /type PerformanceReporter
If the message KAPM04202-I (The hcmdsweb command finished successfully) or

KAPM04118-E (Program type is not registered.) is displayed, go to step (3) in section
3-h.5.2.3.

section 3-h.5.2.3.
If the hcmdscancel command does not exist, go to step (4) in section 3-h.5.2.3.
# Command
If the file does not exist, go to section 3-h.5.2.4.
# File Name
3-h.5.2.4 Uninstalling the Collection Manager component

(1) Execute the Collection Manager uninstaller .
# File Name

If the file does not exist, go to step (3) in section 3-h.5.2.4.If the file does not exist, some of the
Manager server, perform the procedure described in section 3-h.5.2.12.

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.
If neither registry key exists, go to section 3-h.5.2.5.
# Registry Key
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersio
n\Uninstall\<Collection Manager-GUID>
Figure 3-h.5.2.4-1: Successful uninstallation termination window
g) After executing the uninstaller, go to step (3) in section 3-h.5.2.4.

procedure described in section 3-h.5.2.12.
(2) Make sure that Collection Manager has been uninstalled.


# Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGT0(The last
3
value is a zero.)
4
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_0S(The
5
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PC
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PE
8 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PH
9 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PM
10 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PN
11 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PP
12 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PS
13 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PT
14
Application\PFM
15
Application\PFM-HealthCheck
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVer
16
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.
# Registry Key
3 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGT0(The last value is a zero.)
4
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.
# Shared file name

1 %SystemRoot%\SysWOW64\htmjpccomm.dll
2 %SystemRoot%\SysWOW64\jpcaudit{vvrrss}.dll
3 %SystemRoot%\SysWOW64\jpccomm{vvrrss}.dll
4 %SystemRoot%\SysWOW64\jpccommhcc.dll
5 %SystemRoot%\SysWOW64\jpccoommhccjp.dll
6 %SystemRoot%\SysWOW64\jpcodbc.dll

3-h.5.2.5 Uninstalling the Tuning Service component

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.
If this key does not exist, go to step (2) in section 3-h.5.2.5.
# Registry Key
{89331AB6-2E76-4986-9458-54795EF060A0}
(2) Make sure that Tuning Service has been uninstalled.
# Registry Key
1
HiCommandTuningService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\
2
HTM-Tuning Service
3
{89331AB6-2E76-4986-9458-54795EF060A0}
3-h.5.2.6 Uninstalling the Performance Reporter component

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 information in a version-7 environment:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{465EF71F-B608-4C33-
9E19-D56DDCADC82A}
If this registry key does not exist, go to step (2) in section 3-h.5.2.6.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninst
all\{465EF71F-B608-4C33-9E19-D56DDCADC82A}
values.
# File Name
(2) Make sure that the registry keys indicated below do not exist.
# Registry Key

1
PerformanceReporter64
(When x86 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\HTMPR

2
(When x64 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\HTMPR
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\
3
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
also need to perform the procedures described in this section for version 7.
# Registry Key
1 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerformanceReporter
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\HTMPR
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{465EF71
3
F-B608-4C33-9E19-D56DDCADC82A}
3-h.5.2.7 Uninstalling the Hitachi Command Suite Common Component



# File

1 %SystemDrive%\Program Files (x86)\HiCommand\Base\tmp\HBuninst.exe
Note:
Be sure not to mistake the directory "Base64" for the directory "Base", because they might
be in the same directory.
# Command line
1 HBuninst /X
d) After the dialog box that indicates termination of the command appears, check the
value that was output to the following file.
# File
1 hcmdsrtn.enf
(2).
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
%SystemDrive%\Program Files\HiCommand\Base64\tmp\HBuninst.exe
1
Ver.8.1 or later
%SystemDrive%\Program Files\HiCommand\Base64\tmp\HB64uninst.exe
Note:
# Command line
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.
# File
1 hcmds64rtn.enf
(3).
a) 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.
# Registry Key(For V8 or later)

HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\
1
HiCommand Base 64
2
3
HBase64StgMgmtWebService
4
HBase64StgMgmtSSOService
5
HBase64StgMgmtWebSSOService
6
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\
7
HBase64 Event
8
HBase64 Storage Mgmt Log
9
10
{1345FCD1-713E-4449-8F76-3F6503941040} (*1)(*2)
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.
# Registry Key(For V7 or earlier)

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\
1
HiCommand Base
2
3
HBaseStgMgmtComService
4
HiRDBClusterService_HD0
5
6
Application\HBase Storage Mgmt Log
7
Application\HiRDBEmbeddedEdition_HD0
8
Application\HitachiWebServer
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.
To earlier than V8.0.0

[For x86]
Check the value in "Value data" for the InstallGuid value in
HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\
HiRDBEmbeddedEdition_HD0\<CurrentVersion>.
<CurrentVersion> is equal to the value in "Value data" for the CurrentVersion value
in HKEY_LOCAL_MACHINE\ SOFTWARE\
HITACHI\HiRDBEmbeddedEdition_HD0.
[For x64]
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\
HiRDBEmbeddedEdition_HD0\<CurrentVersion>
in

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\HiRDBEmb
eddedEdition_HD0.
V8.0.0 or later
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\
HiRDBEmbeddedEdition_HD1\<CurrentVersion>
in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\HiRDBEmb
eddedEdition_HD1.
(4) Delete the temporary directories for installation.
# Directory
1 %temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
3-h.5.2.8 Deleting the database files

If the files do not exist, go to step (2) in section 3-h.5.2.8.
# File name
file.
# Property Name

1 db_areapath1
2 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 Deleting directories and registry keys

a) Make sure that the directories indicated below do not exist. If these directories exist, delete
them manually.
# Directory

2
{89331AB6-2E76-4986-9458-54795EF060A0}

3
{639938A4-41F1-4643-c5E9-05B1CAC6DA21}

4
{465EF71F-B608-4C33-9E19-D56DDCADC82A}

5
{1345FCD1-713E-4449-8F76-3F6503941040}

6
{61577C30-8F2D-445E-9E9F-54F65EE419A5}

7


1
2
HiCommandTuningManager64
3
TuningManagerRESTService
4
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
5
also need to perform the steps shown below in the old environment (version 7 or earlier)

1
HiCommandTuningManager
2
Application\TuningManager
3
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
3-h.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.

1 HiCommand Base 64
4 HTMPR
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi
6 JP1PC
7 JP1PCMGR
8 JP1PCAGT0
9 HBase64StgMgmtWebService
10 HBase64StgMgmtSSOService
11 HBase64StgMgmtWebSSOService
12 HiCommandTuningManager64

13 PerformanceReporter64
14 TuningManagerRESTService
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
28 HBase64 Event
29 HBase64 Storage Mgmt Log
31 PFM
32 PFM-HealthCheck
33 TuningManager
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
34 {89331AB6-2E76-4986-9458-54795EF060A0}
35 {639938A4-41F1-4643-c5E9-05B1CAC6DA21}
36 {465EF71F-B608-4C33-9E19-D56DDCADC82A}
37 {1345FCD1-713E-4449-8F76-3F6503941040}
38 {61577C30-8F2D-445E-9E9F-54F65EE419A5}
39 {7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
40 {ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}

1 HiCommand Base
3 HTMPR
4 JP1PC
5 JP1PCMGR
6 JP1PCAGT0
7 HBaseStgMgmtComService
8 HBaseStgMgmtWebService
9 HBaseStorageMgmtWebSSOService
10 HiCommandTuningManager
14 PerformanceReporter
15 HBase Storage Mgmt Log
17 HitachiWebServer
18 HTM-Tuning Service

b) Restart the OS.
3-h.5.2.11 Deleting HiCommand Device Manager authentication information

destinations for the target instance of HiCommand Device Manager.
If this directory does not exist, go to section 3-h.5.2.12.
# Directory
If the hcmdsintg command does not exist, go to section 3-h.5.2.12.
# Command line
1
to the next step. If TuningManager is not included, go to section 3-h.5.2.12.
Output example
Product Name :
DeviceManager
TuningManager
# Command line
hcmds64intg /delete /type TuningManager /user "htnmrepuser" /pass
1
the output results.
# Command line

1
3-h.5.2.12 Installation and uninstallation of Tuning Manager server

The procedure of forcibly delete Tuning Manager server is completed in section 3-h.5.2.11.
However, if any of the following conditions are met, the additional procedure described in
this section must be performed.
The file does not exist in step (2) b) of section 3-h.5.2.4.
The uninstallation of Collection Manager fails in (2) g) of section 3-h.5.2.4.
might remain. Therefore, perform the following procedures sequentially to delete the
information of Tuning Manager server completely.
3-i Deleting Tuning Manager server for Linux (Ver.8 or later)

3-i.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):
3-i.2 Applicable Versions

Tuning Manager server for Linux 8.0.0-00 or later
3-i.3 Overview of deleting Tuning Manager server

Figure 3-i.3-1 shows an overview of the process for deleting Tuning Manager server.

START

No
Agents?
Yes Forcibly Deleting

Stopping services.

Was the
No HiRDB.
uninstallation
successful?
No
Yes
Is the
/tmp/hcmdsrtn.enf
value 0?
END Yes
Restarting the OS
Deleting packages
Restarting the OS

END
Figure 3-i.3-1 The flow of the deletion of the Tuning Manager server

Notes:
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
- 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.
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 Deleting Tuning Manager server without deleting Agent


1 $CM_NOUNINST 1

results are output to log files in the /var<TuningManager-Installation-directory>/logs directory.


h_mm_ss}.trc log

Make sure that the following environment variable has not been specified.
1 $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 Forcibly Deleting Tuning Manager server

3-i.5.1 Stopping Services
(1) Execute the commands indicated below to stop the Hitachi Command Suite-related services.
If these commands do not exist, go to section 3-i.5.2.
# Command
1 cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
2 ./hcmdssrv stop
# Command
1 ./hcmds64srv status
Output results

have not stopped, go to section 3-i.5.2.
3-i.5.2 Preparing for Deletion

If this file does not exist, go to section 3-i.5.3.
# File name Property name
1 <HBase32-Installation-directory>/conf/hcmdsdbinit.ini initpath
2 <HBase64-Installation-directory>/conf/hcmdsdbinit.ini initpath
3-i.5.3 Executing the Tool for Deleting Common Component and HiRDB


(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.
# Hitachi Command Suite Common Component Installation directory
1 /opt/HiCommand/Base

a) Execute the commands indicated below.
If these commands do not exist, go to step b).
# Command
1 cd <HBase32-Installation-directory>/bin/
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
1 /var<HBase32-Installation-directory>/tmp/HBuninst.sh
# Directories to which you must not copy the file (including subdirectories)
1 <Hitachi-Command-Suite-products-Installation-directory>
2 /opt/jp1pc
3 /var<Hitachi-Command-Suite-products-Installation-directory>
4 /tmp
Note:
The default path of <Hitachi-Command-Suite-products- Installation-directory> is:
/opt/HiCommand
c) Execute the commands indicated below.

# Command
2 ./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.
Output result 1
Output result 2

d) Check the value specified in the following file.
# File
1 /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.
iii) If the value is 2:
The environment is invalid. Correct the service status and other items, perform step (1) c)
in this section again, and then check the value output to the file.
As shown in the following table, the subsequent action depends on the value output to the
file after you re-execute the commands.
Value in the file after Subsequent action
re-execution
0 Go to step (2) in this section.
1
(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.
# Hitachi Command Suite Common Component Installation directory
1 /opt/HiCommand/Base64
a) Execute the commands indicated below.

If these commands do not exist, go to step b).
# Command
1 cd <HBase64-Installation-directory>/sbin/
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

1 To earlier than Ver.8.1
/var<HBase64-Installation-directory>/tmp/HBuninst.sh
Ver.8.1 or later
/var<HBase64-Installation-directory>/tmp/HB64uninst.sh
# Directories to which you must not copy the file (including subdirectories)
1 <Hitachi-Command-Suite-products-Installation-directory>
2 /opt/jp1pc
3 /var<Hitachi-Command-Suite-products-Installation-directory>
4 /tmp
Note:
The default path of <Hitachi-Command-Suite-products- Installation-directory> is:
/opt/HiCommand
c) Execute the commands indicated below.

# Command
1 cd <directory-to-which-HBuninst.sh/HB64uninst.sh-has-been-copied>
2 To earlier than Ver.8.1

./HBuninst.sh /X
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.
Output result 1
Output result 2
d) Check the value specified in the following file.

# File
1 /tmp/hcmds64rtn.enf
i) If the value is 0:
Go to step (3) in this section.
ii) If the value is 1:
iii) If the value is 2:
The environment is invalid. Correct the service status and other items, perform step (2) c)
in this section again, and then check the value output to the file.
As shown in the following table, the subsequent action depends on the value output to the
file after you re-execute the commands.
Value in the file after Subsequent action
re-execution
1
(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
If the values output to hcmds64rtn.enf is 0 Go to section 3-i.5.7.
If the values output to hcmds64rtn.enf is not 0 Go to section 3-i.5.4(1-2).
If hcmds64rtn.enf does not exist
If you performed both steps (1) and (2), perform the steps in the following table.
Condition Subsequent action
If the values output to hcmdsrtn.enf and hcmds64rtn.enf 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 Deleting the OS Settings

(1-1) If the value output to hcmdsrtn.enf is not 0 or the file hcmdsrtn.enf does not exist
[SLES]
Execute i to iii if the following files exist.
/etc/init.d/hicommand-CWS
/etc/init.d/hicommand-SSOS
/etc/init.d/hicommand-DM
/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
2 Files in /etc/rc3.d whose names begin with Knnhicommand-
3 Files in /etc/rc3.d whose names begin with Snnhicommand-
4 Files in /etc/rc5.d whose names begin with Knnhicommand-
5 Files in /etc/rc5.d whose names begin with Snnhicommand-
[RHEL]
# File

15 /etc/init/2248.PDnn.conf(Only RHEL 6.x)
16 /etc/init/2248.penn.conf(Only RHEL 6.x)

NOTE:
If Hitachi Storage Command Suite Common Component is installed in the default location,
<Base-installation-directory> is replaced with "opt.HiCommand.Base".
If Hitachi Storage 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 ".".
(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

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 Files in /etc/init.d whose names begin with hicommand64-
2 Files in /etc/rc3.d whose names begin with Knnhicommand64-
3 Files in /etc/rc3.d whose names begin with Snnhicommand64-
4 Files in /etc/rc5.d whose names begin with Knnhicommand64-
5 Files in /etc/rc5.d whose names begin with Snnhicommand64-
[RHEL]
# File
1 Files in /etc/init.d whose names begin with hicommand64-
2 Files in /etc/rc0.d whose names begin with K01hicommand64-
5 Files in /etc/rc3.d whose names begin with S99hicommand64-
7 Files in /etc/rc5.d whose names begin with S99hicommand64-
9 /etc/init.d/HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.HD
10 /etc/rc0.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
HDB
12 /etc/rc2.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
HDB
HDB

HDB
16 /etc/init/2248.PDnn.conf(Only RHEL 6.x)
17 /etc/init/2248.penn.conf(Only RHEL 6.x)
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 ".".
need to perform the steps shown below in the old environment (version 7 or earlier).

[RHEL6.x, SUSE11]
Delete the following entries that were added to /etc/inittab, if exist them.
Entries to delete
penn: < number
PDnn: < number
PDnn: < number >:respawn: env LD_LIBRARY_PATH=
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdd
[RHEL7.x, SUSE12]
Delete the following entries that were added to /etc/inittab, if exist them.
Entries to delete
penn: < number
PDnn: < number
PDnn: < number >:respawn: env LD_LIBRARY_PATH=
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdd
Delete the files that are related to the HiRDB services.

Be careful of files with the same name that were registered by other products.

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
(c) Delete the files.

Delete the files for which you executed the commands in step (b).
3-i.5.5 Restarting the OS

Restart the OS.
3-i.5.6 Forcibly Stopping the HiRDB Process

If the 32-bit and 64-bit versions of Hitachi Command Suite Common Component are installed,
perform the procedures for both versions.

using.

# Environment variable Value
name
1 PDDIR <Hitachi-Command-Suite-Common-Component-Instal
lation-directory>/HDB
2 PDCONFPATH <Hitachi-Command-Suite-Common-Component-Instal
lation-directory>/HDB/conf
3 LD_LIBRARY_PATH <Hitachi-Command-Suite-Common-Component-Instal
lation-directory>/HDB/lib
1 bash source <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/
pduxenv
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
3 csh/tcsh setenv PDDIR <Hitachi-Command-Suite-Common-Component-Installation-directory>/
HDB
setenv PDCONFPATH <Hitachi-Command-Suite-Common-Component-Installation-dire
ctory>/HDB/conf
setenv LD_LIBRARY_PATH <Hitachi-Command-Suite-Common-Component-Installati
on-directory>/HDB/lib

# Command
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdstop f
# Command
(4) If the <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/lib/servers/pdprcd

process exists in the system, forcibly stop the process.
# Command
3-i.5.7 Deleting Database Files

# File Name
1 <TuningManager-Installation-directory>/inst/db_area.properties
2 <TuningManager-Installation-directory>/inst/db_area_6.properties
file.
# File Name
1 db_areapath1
2 db_areapath2

Delete the directory whose name you wrote down in step (1) of section 3-i.5.2.
If there was no file in step (1) of section 3-i.5.2, go to section 3-i.5.8.
3-i.5.8 Deleting Packages

(1) Delete the HTNM package.
# Command
1 rpm -e HTNM
2 rpm -e htnm-server
(2) Delete the HTMPR package.

# Command
1 rpm e HTMPR

3-i.5.9 Deleting Files and Directories
Delete the following directories, if the following directories exist..
# Directory
5 /opt/jp1pc
6 /etc/.hitachi/HBase
7 /etc/.hitachi/HBase64
8 /etc/.hitachi/HTNM
Delete the following entries from /etc/services.

Entry to delete
commands.
# Command

1 JP1/PFM - Manager
# Command
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
1 /etc/.hitachi

# Files
3-i.5.10 Restarting the OS

Restart the OS.
3-i.5.11 Deleting the Device Manager authentication information.

you forcibly deleted was connected to an instance of Device Manager on a remote host. This
procedure must be performed on the remote host.
destinations for the target instance of Device Manager.
(1) Delete the Device Manager authentication information.

# Directory
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin

If the hcmds64intg command does not exist, the procedure ends.
# Command line
1 hcmds64intg -print -user "htnmrepuser" -pass " INTERNAL HRXJIHVZ"
Output example
Product Name :
DeviceManager
TuningManager

# Command line
hcmds64intg -delete -type TuningManager -user "htnmrepuser" -pass " INTERNAL
1
HRXJIHVZ"

the output results.
# Command line
1 hcmds64intg -print -user "htnmrepuser" -pass " INTERNAL HRXJIHVZ"

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
1 RAID Agent 8.0.0-00 or later Windows
2 Agent for Server System 8.0.0-00 or later Windows
3 Switch Agent 8.0.0-00 or later Windows
4 NAS Agent 8.0.0-00 or later Windows
5 Oracle Agent 8.0.0-00 or later Windows
6 SQL Agent 8.0.0-00 or later Windows
3-j.3 Notes for the operation

(1) If you delete the agent information by the procedure described in the chapter 3-j, all the programs
of Hitachi Tuning Manager installed on the same server should be deleted. You cannot delete the
target program of Hitachi Tuning Manager only.
procedure described in the chapter 3-j. so make sure that you re-install the agents which were
agent information first by following the procedure described in the chapter 3-j, After that, to delete
the Tuning Manager server information, perform the procedure in 3-h.

3-j.4 The flow of the force deletion and re-install the agent
Figure 3-j.4-1 shows the flow of the deletion of the agent and the flow of re-install the agent.
Start
The procedure of force deletion

Uninstaller No of the agent
Normally End
Yes
Stop the agent related service
Reboot the OS
Both conditions
No
in (*1) met?
Yes
Use the htnmagtregclean Manually delete the registry

command to delete the registry key
Reboot the OS
(*1) : The htnmagtregclean command (version 2.0.0) can only be used if

both of the following conditions are met:
(a) Windows Server 2008 (x86/x64) or Windows Server 2012 is
Install the Agent being used.
(b) Every Agent instance version is from 8.0.0-00 or later
End
Figure 3-j.4-1 The flow of the deletion of the agent and re-install the agent

3-j.5 Uninstall by the uninstaller
Uninstall the agent by following with the procedure described in the manual Hitachi
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 Force deletion of the agent

3-j.6.1 Stop the agent related service
(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.

1 HBase 64 Storage Mgmt Common Service
11 PFM - Correlator
18 PFM - Agent for xxxx yyyy
19 PFM - Agent Store for xxxx yyyy
20 Tuning Manager - Agent REST Application Service
21 Tuning Manager - Agent REST Web Service

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 Type of the agent Single or Multi Instance

1 RAID Agent RAID Multi Instance
2 Agent for Server System *1 RAID Map Single Instance
Windows Single Instance
MSExchange Single Instance
3 Switch Agent SANSwitch Multi Instance
4 NAS Agent NAS Multi Instance
5 Oracle Agent Oracle Multi Instance
6 SQL Agent Microsoft(R) SQL Server Multi Instance
[*1] Agent for Server System consists of 3 agents, RAID Map/Windows/Exchange agent.
(2) Reboot the OS

Reboot the OS so that the agent related service should stop.
3-j.6.2 Delete the file/directory

(1) Delete the Tuning Manager API Component.
(a) Open a command prompt.
(b) Open the following file by using a text editor, and copy the character string of the second line as
UninstallString-command. If the file does not exist, go to step (2) in section 3-j.6.2.
# File Name
1 <Agent Installation Directory>\htnm\Rest\system\insresult.dat
(c) Paste the character string of the second line into the command prompt, and then execute the
command. The uninstallation will start.
1 {UninstallString-command}
(2) Get the information of the installation directory of the agent

(a) Open the registry editor by executing the regedit command.

(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
1 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC\PathName
<Windows (x64)>
# Registry Key
1 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) Delete the agent installation directory

Open the command prompt and execute the following OS command.
Specify the directory path got in the chapter 3-j.6.2 (2) as the <Agent Installation
Directory>.
# Command
1 rd /S /Q <Agent Installation Directory>
3-j.6.3 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
1 Windows Server 2008 x86 -
# Agent Version
1 RAID Agent 8.0.0-00 or later
2 Agent for Server System 8.0.0-00 or later
3 Switch Agent 8.0.0-00 or later
4 NAS Agent 8.0.0-00 or later

5 Oracle Agent 8.0.0-00 or later
6 SQL Agent 8.0.0-00 or later
The following are notes on using the htnmagtregclean command.
# Notes
1 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.
2 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
3 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 (n : Total number of agent instances)
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
5 After you execute the htnmagtregclean command, delete the log file.
6 During execution, do not cancel the htnmagtregclean command by Windows operations such

The htnmagtregclean command can be used to delete the following registry keys:
<Windows (x86)>
# Registry Key
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService
instance name.
<Windows (x64)>
# Registry Key
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.
(2) Execute the htnmagtregclean command.
# Command
1 htnmagtregclean
(3) The following message appears in the command prompt.

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

0 Normal termination code
1 Warning termination code. (One or more registries were not deleted.)
(a) An end code value of 1
Information regarding the fact that registry keys could not be deleted is recorded in the log
file. Check the log file. This file is located directly under the system drive.
# Log File
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 Action
1 A user without administrator Log in as a user that belongs to the Administrators
privileges attempted to execute the group, and then re-execute the htnmagtregclean
htnmagtregclean command. command.
2 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
for Delete Permission. permission settings of the registry key.
3 A registry key has been locked. Using the service control manager, specify Manual
as the Startup type for agent-related services.
Reboot 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 privileges to administrator privileges. Use the elevated command
execute the htnmagtregclean prompt to re-execute the htnmagtregclean command.
command.

(5) After using the htnmagtregclean command to delete the registry keys, delete the log file.
# Log File
Below is the format of log data output.
< Format >
Date Time Loglevel Message

Loglevel:
(I) : Information
(W) : Warning
(E) : Error
<Message displayed if a registry key is successfully deleted>

Wed 01/06/2010 12:01:38.33 (I) The following registry key was removed successfully:
<Message displayed if an attempt to delete a registry key fails>

Wed 01/06/2010 12:01:38.33 (W) An attempt to remove the following registry key has failed:

3-j.6.4 Delete the registry key (Manually deleting the registry keys)
(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
instance name.
<Windows (x64)>
# Registry Key
instance name.
3-j.6.5 Reboot the OS

Reboot the OS.

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
1 RAID Agent 8.0.0-00 or later Solaris (SPARC)/Solaris (x64)/
HP-UX/AIX/Linux
2 Agent for Server System 8.0.0-00 or later Solaris (SPARC)/Solaris (x64)/HP-UX/AIX/Linux
3 Switch Agent 8.0.0-00 or later Linux
4 NAS Agent 8.0.0-00 or later Linux
5 Oracle Agent 8.0.0-00 or later Solaris (SPARC)/Solaris (x64)/HP-UX/AIX/Linux
6 DB2 Agent 8.0.0-00 or later AIX/Linux
7 EAP Agent 8.0.0-00 or later Solaris(SPARC), HP-UX
(*1) Including its bug fix version
3-k.3 Notes for the operation

(1) If you delete the agent information by the procedure described in the chapter 3-k, all the
programs of Hitachi Tuning Manager installed on the same server should be deleted. You cannot
delete the target program of Hitachi Tuning Manager only.
procedure described in the chapter 3-k. so make sure that you re-install the agents which were
agent information first by following the procedure described in the chapter 3-k, and then delete the
Tuning Manager server information by following the procedure described in the chapter 3-i.

3-k.4 The flow of the force deletion and re-install the agent
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 The procedure of force deletion
Normally End of the agent
Yes
Reboot the OS
Install the Agent
End
Figure 3-k.4-1 The flow of the deletion of the agent and re-install the agent
3-k.5 Uninstall by the uninstaller

Uninstall the agent by following with the procedure described in the following manual:
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.

3-k.6 Force deletion of the agent
3-k.6.1 Stop the agent related service
(1) Stop the services of Tuning Manager Agents
(a) Execute the following command in the console.
# Command
2 ./jpcstop all
(b) Execute the following command in the console.

# Command
1 cd /opt/jp1pc/htnm/bin
2 ./htmsrv stop -all
(2) Change the setting of the service automatically started

# Command
1 rm -rf /opt/jp1pc/jpc_start
For AIX:
rmitab jp1pc
2
For SUSE Linux:
chkconfig jp1_pc off
(b) Execute the following OS command in the console.

# Command
For AIX:
rmitab AgtRestApp
rmitab AgtRestWebSrv
1
For SUSE Linux:
chkconfig --del htnm_agent_rest_app
chkconfig --del htnm_agent_rest_webservice
(3) Reboot the OS

(4) Stop the service of Tuning Manager server
In UNIX, if Tuning Manager server is also installed into the server where the agent is
installed, stop the service of Tuning Manager server.
# Command
1 For Solaris:
For Linux:
2 ./hcmds64srv -stop
3-k.6.2 Delete the file/directory

(1) Delete the Tuning Manager API Component.
(a) Check whether the following file exists. If the file does not exist, go to step (2) in section
3-k.6.2.
# File Name
1 <Agent Installation Directory>/htnm/Rest/system/PSB_INST.INF
(b) Execute the following command in the console.
# Command
(c) Execute the following command in the console. The uninstallation will start in the console.
1 For Linux:
/etc/hitachi_x64setup -f -e -u -t "<Agent Installation
Directory>/htnm/Rest/system/PSB_INST.INF"
For AIX and HP-UX:

/etc/hitachi_setup -f -e -u -t "<Agent Installation
Directory>/htnm/Rest/system/PSB_INST.INF"

If these files do not exist, go to section 3-k.6.2(3).

(a) Solaris
# File
(b) Linux
# File
2 Files in /etc/init.d whose names begin with htnm_agent_rest
3 Files in /etc/rc0.d whose names begin with K01htnm_agent_rest
7 Files in /etc/rc3.d whose names begin with S99htnm_agent_rest
11 Files in /etc/rc5.d whose names begin with S99htnm_agent_rest
(c) HP-UX
# File
1 Files in /sbin/init.d whose names begin with hicommand-
2 Files in /sbin/init.d whose names begin with htnm_agent_rest
3 Files in /sbin/rc1.d whose names begin with K090htnm_agent_rest
4 Files in /sbin/rc2.d whose names begin with K910htnm_agent_rest
5 Files in /sbin/rc2.d whose names begin with S910htnm_agent_rest
(d) AIX
# File
1 Files in /etc whose names begin with hicommand-
2 Files in /etc whose names begin with rc.htnm_agent_rest
(3) Delete the installation directory of the agent

# Command
1 rm -rf /opt/jp1pc

3-k.6.3 Reboot the OS
Reboot the OS.

Appendix 4 Knowledge for HiRDB Management
4-a Confirmation of the state of RD area
When it is likely that RD area is closed, confirm the state of an RD area in the following procedures.
[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".
< When the status is not "Started" >

On the Service Settings window, select the following service and start the service by selecting
"Start" in "Action" menu.
Then, confirm that the status of the service is "Started".
2. Open a Command Prompt.

Note: Run all the following commands on the same Command prompt.
3. Change current directory to "bin" directory of Hitachi Storage Command Suite Common
Component.
cd <Suite Install-dir>\bin
4. Execute the following command to start DB.

hcmdsdbsrv /start
Hcmds64dbsrv /start
< When failed to start DB >

Operate procedure 1 again, and operate procedure 4. If procedure 4 operation fails again, cancel
operation, collect logs, then contact the support department.
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
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
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 >
"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
execute "set PDDIR" command and confirm that the variable was defined correctly.
set PDDIR=<Suite Install-dir>\HDB

c) Execute "set PDCONFPATH" command and confirm that the result is following.
<Suite Install-dir>\HDB\CONF
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
execute "set PDUXPLDIR" command and confirm that the variable was defined correctly.
set PDUXPLDIR=<Suite Install-dir>\HDB\UXPLDIR
7. Confirm the state of RD area

Execute the following commands on the Command prompt where "pdntcmd" was executed in
procedure 8.
Change current directory to "bin" directory of the install directory of Hitachi Storage Command
Suite Common Component database.
cd <Suite Install-dir>\HDB\BIN
Execute the following command and confirm the state of RD area.

a) In Ver.5 or earlier
pddbls -r RDUSAGE -l
pddbls -r RDSTATIC -l
pddbls -r RDTRANSIENT -l
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
1 CLOSE 11 HOLD(INQ)
2 CLOSE HOLD 12 HOLD(CMD)
3 CLOSE HOLD (INQ) 13 HOLD(BU)
4 CLOSE HOLD(CMD) 14 HOLD(BU I)
5 CLOSE HOLD(BU) 15 HOLD(BU W)
6 CLOSE HOLD(BU I) 16 HOLD(BU IW)

7 CLOSE HOLD(BU W) 17 ACCEPT-HOLD
8 CLOSE HOLD(BU IW) 18 OPEN
9 CLOSE ACCEPT-HOLD
10 HOLD
4-b Handling of the blocked RD area

Follow the procedure described in Appendix 4-a Confirming the state of the RD area to check the
state of the RD area.
If the RD area is blocked, collect the appropriate logs and contact the Support Center. For details on
how to collect logs, see 4. RAS Collection.
4-c How to extend or reduce the database log area

4-c.1 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.
Alphabet (For Windows/Solaris)
Period (For Windows)
Space (For Windows)
( ) (For Windows )
Colon (For Windows, only for specifying the drive name)
Back Slush (For Windows, for specifying the directory relationship between the parent

and the child directory).
Slush (For Solaris, for specifying the directory relationship between the parent and the
child directory).
Following is the example of < Extended directory>
For Windows C:\win32app\hitachi\hirdb_s\spool\tmp
For Solaris /home/app/hitachi/hirdb/spool/tmp
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

HiCommand Tuning Manager for Windows/Solaris (Version 6.0.0)
[Note] HDS version only
4-c.3 How to extend the size of the database log are

4-c.3.1 Stop the service of Hitachi Storage Command product
Stop the service of all Hitachi Storage Command Suite.
For how to stop the service of Tuning Manager server, refer to the manual.
For how to stop the service of the other Hitachi Storage Command Suite, refer to the manual of
each products.
4-c.3.2 Extend the database log area

(1) Open the command prompt.
(2) Set the environmental variables
How to set the environmental variable is different between Windows and Solaris.
See (2-1) for Windows, (2-2) for Solaris.
(2-1) For Windows

# Command
1 cd /d "<Suite Install-dir>\HDB\bin"
2 pdntcmd
command
# Command
1 set PDDIR
(2-2) For Solaris
export PDDIR
export PDCONFPATH
export PATH


command
# Command
1 env | grep PDDIR
Display result
(3) Add the database log file
(a) Execute the following command for the creation of the file system to which database log file is
stored.
Nothing is output when the command successfully ends.
# Command
1 pdfmkfs -r -n 505 -l 10 -k SYS <Extended directory>\rdX1
(b) Create the database log file by executing the following command
Nothing is output when the command successfully ends.
# Command
1 pdloginit -d sys -f <Extended directory>\rdX1\lg7 -n 500000

(c) Confirm that database log file is successfully created by executing the following command
# Command
1 pdfls -x <Extended directory>\rdX1
Display result
lg7
# Command
Display result
lg8
# Command
Display result
lg9
# Command
Display result
lg10

# Command
Display result
lg11
# Command
Display result
lg12
(d) Edit the database configuration file
i) Back up the sds01 file
The location of sds01 file is as follows.
Windows
Solaris
/opt/HiCommand/Base/HDB/CONF

ii) Open the sds01 file with text editor.
iii) Add the following definition at the end of the sds01 file
pdlogadfg -d sys -g log7 ONL
pdlogadpf -d sys -g log7 -a \

<Extended directory>rdX1\lg7

<Extended directory>\rdX2\lg8




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

v) Confirm that the message is output like Display result by executing the following
command.
# Command
1 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
1 pdlogls -d sys
Display result
HOSTNAME : NUCSTG02(******)
***** Off-line Information *****
Group Type Server Gen No. Status Run ID Block No. Ex-Status
log1 sys sds01 1 cnu---u 44ffbe81 1 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 0 0 --------
log8 sys sds01 0 cn----- 00000000 0 0 --------
log9 sys sds01 0 cn----- 00000000 0 0 --------
log10 sys sds01 0 cn----- 00000000 0 0 --------
log11 sys sds01 0 cn----- 00000000 0 0 --------
log12 sys sds01 0 cn----- 00000000 0 0 --------

4-c.3.3 Start the service of HiRDB
(1) Start the service of HiRDB by executing the following command.
# Windows
1 cd /d "<Suite Install-dir>\bin"
2 [ In Ver.6 to earlier than 8 ]

hcmdsdbsrv /start
hcmds64dbsrv /start
# Solaris
1 cd /opt/HiCommand/Base/bin
2 ./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

hcmdsdbsrv /status
# Solaris
1 ./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 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 Back to the size of the database area to the original

4-c.4.1 Stop the service of all Hitachi Storage Command Suite
Stop the service of all Hitachi Storage Command Suite.
For how to stop the service of Tuning Manager server, refer to the manual Hitachi Tuning
Manager Software Administration Guide.
For how to stop the service of the other Hitachi Storage Command Suite products, see the
manual of each product.
4-c.4.2 Change the size of the database log area to the default
(1) Open the command prompt.
(2) Set the environmental variables
How to set the environmental variable is different between Windows and Solaris. See (2-1) for
Windows, (2-2) for Solaris.
(2-1) For Windows
# Command

1 cd /d "<Suite Install-dir>\HDB\bin"
2 pdntcmd
command
# Command
1 set PDDIR
Display result
PDDIR=<Suite Install-dir>\HDB

(2-2) For Solaris
export PDDIR
export PDCONFPATH
export PATH
etenv LD_LIBRARY_PATH /opt/HiCommand/Base/HDB/lib
command
# Command
1 env | grep PDDIR
Display result

(3) Change the status of the database log file
(a) Execute the following command line by line.
# Command
1 pdlogchg -d sys -g log7
[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
(b) Edit the database configuration file
i) Back up the sds01 file
The location of sds01 file is as follows.
Windows
Solaris
/opt/HiCommand/Base/HDB/CONF

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
1 pdconfchk
Display result
KFPS05007-I System definition check ended. return code = 0
(4) Delete the database log file
(a) Delete the database log file by executing the following command.
# Command
1 pdlogrm -d sys -f <Extended directory>\rdX1\lg7

(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
1 pdfls <Extended directory>\rdX1
(5) Delete the file system to which the database log file is stored by executing the following
command.
# Command
1 del <Extended directory>\rdX1
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.

# Command
1 pdlogls -d sys
Display result
HOSTNAME : NUCSTG02(******)
***** Off-line Information *****
Group Type Server Gen No. Status Run ID Block No. Ex-Status
log1 sys sds01 1 cnu---u 44ffbe81 1 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 --------
4-c.4.3 Start the service of HiRDB

(1) Start the service of HiRDB by executing the following command.
# Windows
1 cd /d "<Suite Install-dir>\bin"

hcmdsdbsrv /start
hcmds64dbsrv /start
# Solaris
1 cd /opt/HiCommand/Base/bin
2 ./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

hcmdsdbsrv /status
# Solaris
1 ./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.
Appendix 5 Data Exporting Sample Script(Ver.6 or later)


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 Hitachi Tuning Manager HP StorageWorks XP Tuning
. Names Manager
2. 2 Hitachi Device Manager Software XP Command View AE Device
. Manager
3. 3 Hitachi Tuning Manager - Agent for HP StorageWorks XP Tuning
. Server System Manager - Agent for Server System
. Oracle Manager - Agent for Oracle
. RAID Manager - Agent for RAID
6. 6 Hitachi Tuning Manager - Agent for None(Only the Hitachi version)
. Network Attached Storage
. SAN Switch Manager - Agent for SAN Switch
. Microsoft(R) SQL Server Manager - Agent for Microsoft(R)
SQL Server
. IBM(R) DB2(R) Universal Manager - Agent for IBM(R)
Database DB2(R) Universal Database
10. Component Common Component XP Command View AE Suite
0 Names Common Component
.
11. Abbreviation HTnM TunMgr
.
12. HDvM Device Manager
13. Default %SystemDrive%\Program %SystemDrive%\Program
2 installation Files\HiCommand\TuningManager Files\CVXPAE\TuningManager
. directory for
Tuning
Manager
server (For
Windows
Server 2003
(x86) and
Windows
Server 2008
(x86))
14. Default %SystemDrive%\Program Files %SystemDrive%\Program Files
installation (x86) \HiCommand\TuningManager (x86) \CVXPAE\TuningManager
directory for
Tuning
Manager
server (For
Windows
Server 2003
(x64) and
Windows
Server 2008
(x64))
installation Files\HiCommand\Base Files\CVXPAE\Base
directory for
Common
Component
(For Windows
Server 2003
(x86) and
Windows
Server 2008
(x86))
installation (x86) \HiCommand\Base (x86) \CVXPAE\Base
directory for
Common
Component
(For Windows
Server 2003
(x64) and
Windows
Server 2008
(x64))

17. Related Hitachi Tuning Manager Software HP StorageWorks XP Tuning
3 documents Agent Administration Guide Manager software agent
. administration guide
18. Hitachi Tuning Manager Software HP StorageWorks XP Tuning
4 Server Administration Guide Manager software server
. administration guide
5 User's Guide Manager software user's guide
.
6 Hardware Reports Reference Manager software hardware reports
. reference
7 Operating System Reports Reference Manager software operating system
. reports reference
8 Application Reports Reference Manager software application reports
. reference
23. 2 Hitachi Tuning Manager Software HP StorageWorks XP Tuning
0 Command Line Interface Guide Manager software CLI user guide
.
24. 2 Hitachi Tuning Manager Software HP StorageWorks XP Tuning
Installation Guide Manager software installation and
. configuration guide
25. 2 Subsystem Lightning 9910/9960 StorageWorks XP48/XP512
2 Names
.
26. 2 Lightning 9970V/9980V StorageWorks XP128/XP1024
3
.
27. 2 NSC55 StorageWorks XP10000
4
.
28. 2 - StorageWorks XP SVS200
5
.
29. 2 USP100/USP600/USP1100 StorageWorks XP12000
6
.
30. 2 USP V StorageWorks XP24000
7
.
31. 2 USP_VM StorageWorks XP20000
8
.
32. 2 Thunder 9200 None(Only the Hitachi version)
9
.
33. 3 Thunder 9500 series None(Only the Hitachi version)
0 Thunder 9520V/Thunder 9530V/
. Thunder 9570V/Thunder 9580V/
Thunder 9585V
34. AMS series None(Only the Hitachi version)
AMS200/AMS500/AMS1000
35. AMS2000 series None(Only the Hitachi version)
AMS2100/AMS2300/AMS2500
36. SMS100 None(Only the Hitachi version)
37. WMS100 None(Only the Hitachi version)
38. 3 Command hcmdsgetlogs Cvxpaegetlogs
2 Names
.
39. 3 Service HiCommand Suite TuningManager StorageWorks XP Tuning Manager
4 Names
.
40. 3 HiCommand Suite TuningService StorageWorks XP Tuning Service
5
.
41. 3 HiCommand Performance Reporter StorageWorks XP Performance
6 Reporter
.
42. 3 Start menu Start, Programs, Hitachi Storage Start, Programs, XP Command View
9 Command Suite AE
.
43. File Names 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

[In Ver.7]
1. Product Hitachi Tuning Manager HP StorageWorks P9000 Tuning
. Names Manager
or
HP P9000 Tuning Manager
2. 2 Hitachi Device Manager Software HP StorageWorks P9000 Command
. View AE Device Manager
or
HP P9000 Command View AE
Device Manager
3. 3 Hitachi Tuning Manager - Agent for HP StorageWorks P9000 Tuning
. Server System Manager - Agent for Server System
. Oracle Manager - Agent for Oracle
. RAID Manager - Agent for RAID
6. 6 Hitachi Tuning Manager - Agent for None(Only the Hitachi version)
. Network Attached Storage
. SAN Switch Manager - Agent for SAN Switch
. Microsoft(R) SQL Server Manager - Agent for Microsoft(R)
SQL Server
. IBM(R) DB2(R) Universal Manager - Agent for IBM(R)
10. Hitachi Tuning Manager - Agent for HP StorageWorks P9000 Tuning
Enterprise Applications Manager - Agent for Enterprise
Applications
11. Component Common Component XP Command View AE Suite
0 Names Common Component
.
.
13. HDvM Device Manager
2 installation Files\HiCommand\TuningManager Files\CVXPAE\TuningManager
. directory for
Tuning
Manager
server (For
Windows
Server 2003
(x86) and
Windows
Server 2008
(x86))
installation (x86) \HiCommand\TuningManager (x86) \CVXPAE\TuningManager
directory for
Tuning
Manager
server (For
Windows
Server 2003
(x64) and
Windows
Server 2008
(x64))
directory for
Common
Component
(For Windows
Server 2003
(x86) and
Windows
Server 2008
(x86))
installation (x86) \HiCommand\Base (x86) \CVXPAE\Base
directory for
Common
Component
(For Windows
Server 2003
(x64) and

Windows
Server 2008
(x64))
18. Related Hitachi Tuning Manager Software HP StorageWorks P9000 Tuning
3 documents Agent Administration Guide Manager Software Agent
. Administration Guide
19. Hitachi Tuning Manager Software HP StorageWorks P9000 Tuning
4 Server Administration Guide Manager Software Server
. Administration Guide
5 User's Guide Manager Software User Guide
.
6 Hardware Reports Reference Manager Software Hardware Reports
. Reference
7 Operating System Reports Reference Manager Software Operating System
. Reports Reference
8 Application Reports Reference Manager Software Application
. Reports Reference
24. 2 Hitachi Tuning Manager Software HP StorageWorks P9000 Tuning
0 Command Line Interface Guide Manager Software CLI User Guide
.
25. 2 Hitachi Tuning Manager Software HP StorageWorks P9000 Tuning
Installation Guide Manager Software Installation Guide
.
26. 2 Subsystem Lightning 9910/9960 StorageWorks XP48/XP512
2 Names
.
27. 2 Lightning 9970V/9980V StorageWorks XP128/XP1024
3
.
28. 2 NSC55 StorageWorks XP10000
4
.
29. 2 - StorageWorks XP SVS200
5
.
30. 2 USP100/USP600/USP1100 StorageWorks XP12000
6
.
31. 2 USP V StorageWorks XP24000
7
.
32. 2 USP_VM StorageWorks XP20000
8
.
33. VSP StorageWorks P9500
34. 2 Thunder 9200 None(Only the Hitachi version)
9
.
35. 3 Thunder 9500 series None(Only the Hitachi version)
0 Thunder 9520V/Thunder 9530V/
. Thunder 9570V/Thunder 9580V/
Thunder 9585V
AMS2100/AMS2300/AMS2500
38. S SMS100 None(Only the Hitachi version)
39. HUS100 series None(Only the Hitachi version)
HUS110/HUS130/HUS150
41. 3 Command hcmdsgetlogs Cvxpaegetlogs
2 Names
.
42. 3 Service HiCommand Suite TuningManager Tuning Manager
4 Names
.
43. 3 HiCommand Suite TuningService Tuning Service
5
.
44. 3 HiCommand Performance Reporter Performance Reporter
6
.
45. 3 Start menu Start, Programs, Hitachi Storage Start, Programs, XP Command View
9 Command Suite AE
.

[In Ver.8 to earlier than 8.4.0]

1. Product Hitachi Tuning Manager HP XP7 Tuning Manager
Names
2. Hitachi Device Manager HP XP7 Command View Advanced
Edition
3. Hitachi Tuning Manager - Agent for HP XP7 Tuning Manager - Agent for
Server System Server System
Oracle Oracle
RAID RAID
6. Hitachi Tuning Manager - Agent for None(Only the Hitachi version)
Network Attached Storage
SAN Switch SAN Switch
Microsoft(R) SQL Server Microsoft(R) SQL Server
IBM(R) DB2(R) Universal IBM(R) DB2(R) Universal
Database Database
Enterprise Applications Enterprise Applications
11. Component Common Component HP XP7 Command View AE
Names Common Component
13. HDvM DevMgr
installation Files\HiCommand\TuningManager Files\CVXPAE\TuningManager
directory for
Tuning
Manager
server (For
Windows

Server 2003
(x64) and
Windows
Server 2008
(x64))
directory for
Common
Component
(For Windows
Server 2003
(x64) and
Windows
Server 2008
(x64))
16. Related Hitachi Command Suite Tuning HP XP7 Tuning Manager Agent
documents Manager Agent Administration Administration Guide
Guide
17. Hitachi Command Suite Tuning HP XP7 Tuning Manager Server
Manager Server Administration Administration Guide
Guide
18. Hitachi Command Suite Tuning HP XP7 Tuning Manager User Guide
Manager User Guide
19. Hitachi Command Suite Tuning HP XP7 Tuning Manager API
Manager API Reference Guide Reference Guide
20. Hitachi Command Suite Tuning HP XP7 Tuning Manager Hardware
Manager Hardware Reports Reports Reference
Reference
21. Hitachi Command Suite Tuning HP XP7 Tuning Manager Operating
Manager Operating System Reports System Reports Reference
Reference
22. Hitachi Command Suite Tuning HP XP7 Tuning Manager
Manager Application Reports Application Reports Reference
Reference
23. Hitachi Command Suite Tuning HP XP7 Tuning Manager CLI
Manager CLI Reference Guide Reference Guide
24. Hitachi Command Suite Tuning HP XP7 Tuning Manager Installation
Manager Installation Guide Guide
25. Subsystem Lightning 9910/9960 StorageWorks XP48/XP512
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
33. VSP G1000 XP7 Storage
34. Thunder 9200 None(Only the Hitachi version)
35. Thunder 9500 series None(Only the Hitachi version)
Thunder 9520V/Thunder 9530V/
Thunder 9585V
AMS2100/AMS2300/AMS2500
41. Command hcmdsgetlogs Cvxpaegetlogs
Names
42. Service Names HiCommand Suite TuningManager Tuning Manager
43. HiCommand Performance Reporter Performance Reporter
44. Start menu Start, Programs, Hitachi Command Start, Programs, XP Command View
Suite AE

No. Item HITACHI version HPE OEM version
1. Product Hitachi Tuning Manager Hewlett Packard Enterprise XP7
Names Tuning Manager
2. Hitachi Device Manager Hewlett Packard Enterprise XP7
Command View Advanced Edition
3. Hitachi Tuning Manager - Agent for Hewlett Packard Enterprise XP7
Server System Tuning Manager - Agent for Server
System
Oracle Tuning Manager - Agent for Oracle
RAID Tuning Manager - Agent for RAID
6. Hitachi Tuning Manager - Agent for None(Only the Hitachi version)
Network Attached Storage
SAN Switch Tuning Manager - Agent for SAN
Switch
Microsoft(R) SQL Server Tuning Manager - Agent for
Microsoft(R) SQL Server
IBM(R) DB2(R) Universal Tuning Manager - Agent for IBM(R)
Enterprise Applications Tuning Manager - Agent for
Enterprise Applications
11. Component Common Component Hewlett Packard Enterprise XP7
Names Command View AE Common
Component
13. HDvM DevMgr
installation Files\HiCommand\TuningManager Files\CVXPAE\TuningManager
directory for
Tuning
Manager
server (For
Windows
Server 2003
(x64) and
Windows
Server 2008
(x64))
directory for
Common
Component
(For Windows
Server 2003
(x64) and
Windows
Server 2008
(x64))
16. Related Hitachi Command Suite Tuning Hewlett Packard Enterprise XP7
documents Manager Agent Administration Tuning Manager Agent
Guide Administration Guide
17. Hitachi Command Suite Tuning Hewlett Packard Enterprise XP7
Manager Server Administration Tuning Manager Server
Guide Administration Guide
Manager User Guide Tuning Manager User Guide
Manager API Reference Guide Tuning Manager API Reference
Guide
Manager Hardware Reports Tuning Manager Hardware Reports
Reference Reference
Manager Operating System Reports Tuning Manager Operating System
Reference Reports Reference
Manager Application Reports Tuning Manager Application Reports
Reference Reference
Manager CLI Reference Guide Tuning Manager CLI Reference
Guide
Manager Installation Guide Tuning Manager Installation Guide

25. Subsystem Lightning 9910/9960 StorageWorks XP48/XP512
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
33. VSP G1000 XP7 Storage
34. Thunder 9200 None(Only the Hitachi version)
35. Thunder 9500 series None(Only the Hitachi version)
Thunder 9585V
AMS2100/AMS2300/AMS2500
41. Command hcmdsgetlogs cvxpaegetlogs
Names
42. Service Names HiCommand Suite TuningManager Tuning Manager
43. HiCommand Performance Reporter Performance Reporter
44. Start menu Start, Programs, Hitachi Command Start, Programs, XP Command View
Suite AE

Appendix 7 Backup and Restoration (Ver. 6 or later)
7-a. Backup procedure on a host on which the Tuning Manager server and Agent are installed in
a Windows environment
7-a.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 Windows environment.
7-a.2 Applicable Versions

(1)Tuning Manager server 6.0.0-00 or later
(2)Agent 6.0.0-00 or later
Note: (1) and (2) must be installed on the same host.
7-a.3 Terms
# Terms Folder
Hitachi-StorageCommand-Suite-Common-Component [ In Ver.6 to earlier than 8 ]
-installation-directory <Installation-directory>\Base
1
<Installation-directory>\Base64
2 Hitachi-Tuning-Manager-installation-directory <Installation-directory>\TuningManager
Installation-directory [ In Ver.6 to earlier than 8 ]
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
3
Server 2012:
%SystemDrive%\Program Files (x86)\HiCommand
4 Agent-installation-directory <Installation-directory>\TuningManager\jp1pc
5 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 Overview of Tuning Manager server backup procedure

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.

Start
Described in 7-a.5 Back up data for Hitachi Storage Command
Suite products
Check the free disk space required for backup 7-a.5(1)
Execute the hcmdsbackups command 7-a.5(2)
7-a.6
Back up the definition information files for the Tuning Manager server
7-a.7
Back up the definition information files for Performance Reporter
Back up the definition information files

7-a.7(ii)
for Tuning Manager REST Application Service (Ver. 8 or later)
Described in 7-a.8 Back up the Store database
Start Agent
7-a.8(1)
Execute the jpcctrl backup command 7-a.8(2)
Described in 7-a.9 Back up the Agent definition information files
Stop Agent
7-a.9(1)
Back up the Agent definition information files 7-a.9(2)

for HTnM-Agent REST Services (Ver. 8 or later) 7-a.10
7-a.11
Back up the performance data
for Tuning Manager API (Ver. 8.0 or later)
Back up the Hybrid Store (Ver. 8.1.3 or later) 7-a.12
End
Figure 7-a.7-1 An overview of the procedure for backing up the Tuning Manager server and Agent databases

7-a.5 Back up data for Hitachi Storage Command Suite products
(1) Check the free disk space required for backup
Using the formula below, calculate the free disk space required to back up the data.
Free-disk-space-required-for-backup[gigabytes] =
0.1 + (used-database-capacity-as-reported-by-htm-db-status command + 0.8) * 2
Note: For details about calculating the free disk space required for backup, see the following manual:
- In Ver.6
- In Ver.7
- In Ver.8
The following is an example of calculating disk space requirements.

Execute the htm-db-status command, and determine how much capacity the database uses.
In this example, the used database capacity is 0.16 GB. This means that 2.02 GB of disk space is
required to back up the database.
0.1 + (0.16 + 0.8) * 2 = 2.02GBytes
# Command line
cd <Hitachi-Tuning-Manager-installation-directory>\bin\
htm-db-status
Output example
Area Path:
D:\Program Files\HiCommand\TuningManager\database\TuningManager\TM00
(2) Execute the hcmdsbackups command.

Execute the hcmdsbackups command to back up the data associated with Hitachi
Storage Command Suite products. The data is backed up to the folder specified as the
dir option.
The following shows an example of the hcmdsbackups command execution:

# Command line
1 cd <Hitachi-Command-Suite-Common-Conponent-installation-directory>\bin\
hcmdsbackups /dir d:\backup\hcmdsbackups /auto
hcmds64backups /dir d:\backup\hcmdsbackups /auto
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
- In Ver.7
- In Ver.8
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

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
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.IDX
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.DAT
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
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr\*.IDX
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
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\cli.properties

COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\common.properties
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\system.logging.properties
7-a.7 Back up the definition information files for Performance Reporter

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
- In Ver.7
- In Ver.8
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
"bookmarkRepository" item of the initialization settings file (config.xml) of Performance
Reporter.
The following shows an example of using the Windows XCOPY command to back up
Performance Reporter bookmarks:

# Command line
XCOPY /e /y /i
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>\ -
2 system\ -
3 sysconf\ rest.properties
4 rest_raidinstance_info
5 rest_nasinstance_info
6 rest_host_info
7-a.8 Back up the Store database

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
1 cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
2 jpcstart all
(2) Identify the services to back up

Execute the "jpcctrl list" command. The command outputs a list of services. The services that
contain the letter "S" as the second character of the service ID are backed up.
# Command line
2 jpcctrl list *
(3) Execute the jpcctrl backup command.

Execute the jpcctrl backup command with -d option to back up the Store database.
Create a new data storage destination folder, and then specify the folder with the -d option.
If there are multiple Store databases to be backed up, repeat the backup operation until all of the
databases have been backed up. When performing the backup operation, make sure to change the
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
2 mkdir d:\backup\DS1RAID[host01]
3 jpcctrl backup DS1RAID[host01] -d 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 Back up the definition information files for Agent

(1) Stop Agent.
# Command line
2 jpcstop all
(2) Back up the Agent definition information files.

Use the Windows COPY command to back up the definition information files for
Agent. For a list of the Agent definition information files to back up, see the following
manual:
- In Ver.6
- In Ver.7
- In Ver.8
definition information files for Agent. For this example, the destination folders used by
the COPY command must be created in advance.
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 <Agent-installation-directory>\xxxx\agent\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\xxxx\agent
2 COPY <Agent-installation-directory>\xxxx\agent\instance-name\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\xxxx\agent\instance-name
3 COPY <Agent-installation-directory>\xxxx\store\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\xxxx\store
4 COPY <Agent-installation-directory>\xxxx\store\instance-name\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\xxxx\store\instance-name
5 COPY <Agent-installation-directory>\agtw\agent\agtw.properties
d:\backup\HiCommand\TuningManager\jp1pc\agtw\agent
6 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
1 <Agent-installation-directory>\ -
2 htnm\ -
3 agent\ -
4 config\ apidataglobalconfig.ini
5 alertglobalconfig.ini
6 system\ data_file_manage
(Does not exist if Tuning Manager API is disabled.)
7 Rest\ -
8 config\ user.properties
9 htnm_httpsd.conf
10 system\ -
11 sysconf\ system.properties

7-a.11 Back up the performance data for Tuning Manager API (Ver. 8 or later)
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
1 <Agent-installation-directory>\ -
2 xxxx\ -
3 agent\ -
4 instance-name\ -
5 restdata\ Keeping the directory structure, copy all the
subdirectories and files.
Note: xxxx indicates the service key of each Agent. For details on the service keys of each Agent,
7-a.12 Back up the Hybrid Store (Ver. 8.1.3 or later)

Use the htmhsbackup command to perform the backup. For details, see the Hitachi Command Suite
Tuning Manager Agent Administration Guide.
The following table lists an execution example of the htmhsbackup command in a Windows
environment.
# Command line
1 cd <Agent-installation-directory>\jp1pc\htnm\bin
2 mkdir D:\backup\RAID_backup
3 htmhsbackup -dir D:\backup\RAID_backup

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
- In Ver.7
- In Ver.8
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:
3 for Windows Server 2003 x64, Windows Server 2008 x64 and Windows
Server 2012:
%SystemDrive%\Program Files (x86)\HiCommand
4 Agent-installation-directory <Installation-directory>\TuningManager\jp1pc

5 Platform-Agent-Tuning-Manager-installation-directory <Installation-directory>\TuningManager\jp1pc
default.
7-b.5 Overview of Tuning Manager server restoration

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.
Described in 7-b.6 Restore data for Hitachi Storage Command

Start
Suite products
Execute the hcmdsdb command 7-b.6(1)
Restore the definition information files for the Tuning Manager 7-b.7
Restore the definition information files for Performance Reporter 7-b.8
Restore the definition information files 7-b.8(ii)

for Tuning Manager REST Service (Ver. 8.0 or later)
Described in 7-b.9 Restore the Store database
Stop Agent 7-b.9(1)
Execute the jpcresto command 7-b.9(2)
Restore the definition information files for Agent 7-b.10
Restore the definition information files 7-b.11

for HTnM-Agent REST Services (Ver. 8.0 or later)
Restore the performance data

for Tuning Manager API (Ver. 8.0 or later) 7-b.12
Restore the Hybrid Store (Ver. 8.1.3 or later) 7-b.13
End
Figure 7-b.7-1 An overview of the procedure for restoring the Tuning Manager server and Agent databases

7-b.6 Restore data for Hitachi Storage Command Suite products
(1) Execute the hcmdsdb command.

Execute the hcmdsdb command to restore the data associated with Hitachi Storage Command
Suite products. In the restore option, specify the name of the folder where the backup data is stored.
The following shows an example of the hcmdsdb command execution:
# Command line
1 cd <Hitachi-Tuning-Manager-installation-directory>\bin\
hcmdsdb /restore d:\backup\hcmdsbackups /type ALL /auto
hcmds64db /restore d:\backup\hcmdsbackups /type ALL /auto
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
- In Ver.7
- In Ver.8
The following shows an example of using the Windows COPY command to restore the definition
information files for the Tuning Manager server:
# Command line
1 COPY d:\backup\HiCommand\TuningManager\jp1pc\jpchosts
< Hitachi-Tuning-Manager-installation-directory >\TuningManager\jp1pc
2 COPY d:\backup\HiCommand\TuningManager\jp1pc\*.ini
< Hitachi-Tuning-Manager-installation-directory >\TuningManager\jp1pc

3 COPY d:\backup\HiCommand\TuningManager\jp1pc\bin\action\*.ini
< Hitachi-Tuning-Manager-installation-directory >\jp1pc\bin\action
4 COPY d:\backup\HiCommand\TuningManager\jp1pc\bin\statsvr\*.ini
< Hitachi-Tuning-Manager-installation-directory >\jp1pc\bin\statsvr
5 COPY d:\backup\HiCommand\TuningManager\conf\user.properties
<Hitachi-Tuning-Manager-installation-directory>\conf
6 COPY d:\backup\HiCommand\TuningManager\conf\logging.properties
<Hitachi-Tuning-Manager-installation-directory>\conf
7 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\clator\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\clator
8 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager
9 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.DB
10 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.IDX
11 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.DAT
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
16 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr\*.IDX
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

<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
25 COPY d:\backup\HiCommand\TuningManager\system\sysconf\cli.properties
26 COPY d:\backup\HiCommand\TuningManager\system\sysconf\common.properties
27 COPY d:\backup\HiCommand\TuningManager\system\sysconf\system.logging.properties
7-b.8 Restore the definition information files for Performance Reporter

Use the Windows COPY 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
- In Ver.7
- In Ver.8
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.
# Folder
1 <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.

The following shows an example of using the Windows XCOPY command to copy Performance
Reporter bookmarks, overwriting the files at the destination:
# Command line
1 XCOPY /e /y /I d:\backup\HiCommand\TuningManager\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).
7-b.9 Restore the Store database

When restoring the Store database, make sure to use the same host name and instance name as it was
backed up.
(1) Stop Agent.

# Command line
2 jpcstop all
(2) Execute the jpcresto command.

Execute the jpcresto command to restore the Store database. For the service key specified by the
"jpcresto" command, you must enter the service key that corresponds to the service ID you specified
when backing up data. For details about the correspondence relationship between the service keys
and the service IDs, see Appendix 14-a.
The following shows an example of the jpcresto command execution:
# Command line
2 jpcresto agtd d:\backup\DS1RAID[host01]
Output example

KAVE06006-I Store Restore processing of the Store database terminated normally
Note: For details about the jpcresto command, see the manual.
7-b.10 Restore the definition information files for Agent

procedure is not necessary on an Agent that is operated with Hybrid Store. When restoring the
definition information files for Agent, make sure to use the same host name and instance name as it
was backed up.
(1) Restore the Agent definition information files.

Use the Windows COPY command to copy the backed-up Agent definition information files,
overwriting the files at the destination. For a list of the Agent definition information files to restore,
see the following manual:
- In Ver.6
- In Ver.7
- In Ver.8
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

7-b.11 Restore the definition information files for HTnM-Agent REST Services (Ver. 8.0 or
later)
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)
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.
7-b.13 Restore the Hybrid Store (Ver. 8.1.3 or later)

When you restore the Hybrid Store data, use the same host name and instance name that were used
when you backed up the data.
For details, see the Hitachi Command Suite Tuning Manager Agent Administration Guide.
(1) Stop Agent services

Use the htmsrv command to stop Agent services.
# Command Line
2 htmsrv stop all
(2) Execute the htmhsrestore command

The following table lists execution examples of the htmhsrestore command.
# Command Line
2 htmhsrestore -dir D:\backup\RAID_ backup
(3) Set the environment-dependent information

After executing the htmhsrestore command, see the manual to set the environment-dependent
information, and then make sure that the target is being monitored correctly.

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 [ In Ver.6 to earlier than 8 ]
/opt/HiCommand/Base
1
2 Hitachi-Tuning-Manager-installation-directory /opt/HiCommand/TuningManager
3 Installation-directory /opt/HiCommand
4 Agent-installation-directory /opt/jp1pc
5 Platform-Agent-Tuning-Manager-installation-directory /opt/jp1pc
default.

7-c.4 Overview of Tuning Manager server backup procedure
Start
Described in 7-c.5 Back up data for Hitachi Storage Command
Suite products
Check the free disk space required for backup 7-c.5(1)
7-c.5(2)
Execute the hcmdsbackups command
Back up the definition information files for the Tuning Manager server
7-c.6
Back up the definition information files for Performance Reporter 7-c.7
Back up the definition information files 7-c.7(ii)

for Tuning Manager REST Application Service (Ver.8.0 or later)
Described in 7-c.8 Backing up the Store database
Start Agent 7-c.8(1)
Execute the jpcctrl backup command

7-c.8(2)
Described in 7-c.9 Back up the Agent definition information files
Stop Agent 7-c.9(1)
Back up the Agent definition information files

7-c.9(2)

for HTnM-Agent REST Services (Ver.8.0 or later) 7-c.10
Back up the performance data 7-c.11

for Tuning Manager API (Ver.8.0 or later)
Back up the Hybrid Store (Ver.8.1.3 or later) 7-c.12
End
Figure 7-c.7-1 An overview of the procedure for backing up the Tuning Manager server and Agent databases

7-c.5 Back up data for Hitachi Storage Command Suite products
(1) Check the free disk space required for backup
Using the formula below, calculate the free disk space required to back up the data.
0.1 + (used-database-capacity-as-reported-by-htm-db-status command + 0.8) * 2
Note: For details about calculating the free disk space required for backup, see the following manual:
- In Ver.6
- In Ver.7
- In Ver.8
The following is an example of calculating disk space requirements.

Execute the htm-db-status command, and determine how much capacity the database uses.
In this example, the used database capacity is 0.16 GB. This means that 2.02 GB of disk space is
required to back up the database.
0.1 + (0.16 + 0.8) * 2 = 2.02GBytes
# Command line
1 For Solaris:
cd /opt/HiCommand/TuningManager/bin
For Linux :
cd <TuningManager-Installation-directory>/bin
2 ./htm-db-status
Output example
Area Path:
/TMP/Program Files/HiCommand/TuningManager/database/TuningManager/TM00
(2) Execute the hcmdsbackups command.

Execute the hcmdsbackups command to back up the data associated with Hitachi Storage
Command Suite products. The data is backed up to the folder specified as the dir option.

The following shows an example of the hcmdsbackups command execution:
# Command line
1 For Solaris :
For Linux :
./hcmdsbackups -dir /tmp/backup/hcmdsbackups -auto
./hcmds64backups -dir /tmp/backup/hcmdsbackups -auto
Output example
KAPM05320-I Backup successfully ended : CommonComponent Database.
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
- In Ver.7
- In Ver.8
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

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
25 cp /opt/<TuningManager-Installation-directory>/system/sysconf/cli.properties
26 cp /opt/<TuningManager-Installation-directory>/system/sysconf/common.properties
27 cp /opt/<TuningManager-Installation-directory>/system/sysconf/system.logging.properties
7-c.7 Back up the definition information files for Performance Reporter

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
- In Ver.7
- In Ver.8

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

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 Back up the Store database

(1) Start Agent.
# Command line
2 ./jpcstart all
(2) Identify the services to back up

Execute the "jpcctrl list" command. The command outputs a list of services. The services that
contain the letter "S" as the second character of the service ID are backed up.
# Command line
2 ./jpcctrl list "*"
(3) Execute the jpcctrl backup command.

Execute the jpcctrl backup command with -d option to back up the Store database. Create a new
data storage destination directory, and then specify the directory with the -d option.
If there are multiple Store databases to be backed up, repeat the backup operation until all of the
databases have been backed up. When performing the backup operation, make sure to change the
folder specified with the -d option each time you execute the command.
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.
The following shows an example of the jpcctrl backup command execution:

# Command line
2 mkdir /tmp/backup/DS1RAID[host01]
3 ./jpcctrl backup DS1RAID[host01] -d /tmp/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-c.9 Back up the definition information files for Agent

(1) Stop Agent.
# Command line
2 ./jpcstop all
(2) Back up the Agent definition information files.

Use the Unix cp command to back up the definition information files for Agent. For a list of the
Agent definition information files to back up, see the following manual:
- In Ver.6
- In Ver.7
- In Ver.8
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

7-c.10 Back up the definition information files for HTnM-Agent REST Services (Ver.8.0 or
later)
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)
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.
7-c.12 Back up the Hybrid Store (Ver. 8.1.3 or later)

Use the htmhsbackup command to perform the backup. For details, see the Hitachi Command Suite
Tuning Manager Agent Administration Guide.
The following table lists execution examples of the htmhsbackup command in a UNIX
environment.
# Command Line
2 mkdir /tmp/RAID_backup
3 ./htmhsbackup -dir /tmp/RAID_backup

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
- In Ver.7
- In Ver.8
7-d.3 Applicable Versions

7-d.4 Terms
# Terms Directory
Hitachi-Storage-Command-Suite-Common-Component-installation-directory [ In Ver.6 to earlier than 8 ]
/opt/HiCommand/Base
1
2 Hitachi-Tuning-Manager-installation-directory /opt/HiCommand/TuningManager
3 Installation-directory /opt/HiCommand
4 Agent-installation-directory /opt/Hitachi/jp1pc
5 Platform-Agent-Tuning-Manager-installation-directory /opt/Hitachi/jp1pc
Note: Unless you specify other directories during installation, the above directories are

used by default.
7-d.5 Overview of Tuning Manager server restoration

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.
Described in 7-d.6 Restore data for Hitachi Storage Command

Start
Suite products
Execute the hcmdsdb command

7-d.6(1)
Restore the definition information files for the Tuning Manager 7-d.7
7-d.8
Restore the definition information files for Performance Reporter
Restore the definition information files

for Tuning Manager REST Service (Ver. 8.0 or later) 7-d.8(ii)
Described in 7-d.9 Restore the Store database
Stop Agent
7-d.9(1)
Execute the jpcresto command 7-d.9(2)
Restore the definition information files for Agent 7-d.10
Restore the definition information files 7-d.11

for HTnM-Agent REST Services (Ver. 8.0 or later)
7-d.12
Restore the performance data
for Tuning Manager API (Ver. 8.0 or later)
Restore the Hybrid Store (Ver. 8.1.3 or later) 7-d.13
End
Figure 7-d.7-1 An overview of the procedure for restoring the Tuning Manager server and Agent databases

7-d.6 Restore data for Hitachi Storage Command Suite products
(1) Execute the hcmdsdb command.
Execute the hcmdsdb command to restore the data associated with Hitachi Storage Command
Suite products. In the restore option, specify the name of the folder where the backup data is stored.
The following shows an example of the hcmdsdb command execution:
# Command line
1 For Solaris :
For Linux :
./hcmdsdb /restore /tmp/backup/hcmdsbackups -type ALL -auto
./hcmds64db /restore /tmp/backup/hcmdsbackups -type ALL -auto
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
- In Ver.7
- In Ver.8
The following shows an example of using the UNIX cp command to restore the definition
information files for the Tuning Manager server:
# Command line
1 cp /tmp/backup/opt/jp1pc/jpchosts /opt/jp1pc
2 cp /tmp/backup/opt/jp1pc/*.ini /opt/jp1pc

3 cp /tmp/backup/opt/jp1pc/bin/action/*.ini /opt/jp1pc/bin/action
4 cp /tmp/backup/opt/jp1pc/bin/statsvr/*.ini /opt/jp1pc/bin/statsvr
5 cp /tmp/backup<TuningManager-Installation-directory>/conf/user.properties
<TuningManager-Installation-directory>/conf
6 cp /tmp/backup<TuningManager-Installation-directory>/conf/logging.properties
<TuningManager-Installation-directory>/conf
7 cp /tmp/backup/opt/jp1pc/mgr/clator/*.ini /opt/jp1pc/mgr/clator
8 cp /tmp/backup/opt/jp1pc/mgr/manager/*.ini /opt/jp1pc/mgr/manager
9 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
25 cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/cli.properties
26 cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/common.properties
27 cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/system.logging.properties
7-d.8 Restore the definition information files for Performance Reporter

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

- In Ver.7
- In Ver.8
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
"bookmarkRepository" item of the initialization settings file (config.xml) of Performance
Reporter.
The following shows an example of using the UNIX cp command to copy Performance
Reporter bookmarks, overwriting the files at the destination:
# Command line
1 For Solaris :
cp -r /tmp/backup/opt/HiCommand/TuningManager/PerformanceReporter/bookmarks
/opt/HiCommand/TuningManager/PerformanceReporter
For Linux :

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.
7-d.9 Restore the Store database

When restoring the Store database, make sure to use the same host name and instance name as it was
backed up.
(1) Stop Agent.

# Command line
2 ./jpcstop all
(2) Execute the jpcresto command.

Execute the jpcresto command to restore the Store database. For the service key specified by the
"jpcresto" command, you must enter the service key that corresponds to the service ID you specified
when backing up data. For details about the correspondence relationship between the service key and
the service ID, see Appendix 14-a.
The following shows an example of the jpcresto command execution:

# Command line
2 ./jpcresto agtd /tmp/backup/DS1RAID[host01]
Output example
KAVE06006-I Store Restore processing of the Store database terminated normally
Note: For details about the jpcresto command, see the manual.

7-d.10 Restore the definition information files for Agent
When restoring the definition information files for Agent, make sure to use the same host name and
instance name as it was backed up.
(1) Restore the Agent definition information files.

Use the Unix cp command to copy the backed-up Agent definition information files, overwriting
the files at the destination. For a list of the Agent definition information files to restore, see the
following manual:
- In Ver.6
- In Ver.7
- In Ver.8
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
7-d.11 Restore the definition information files for HTnM-Agent REST Services
(Ver. 8.0 or later)
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.

7-d.12 Restore the performance data for Tuning Manager API (Ver. 8.0 or later)
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.
7-d.13 Restore the Hybrid Store (Ver. 8.1.3 or later)

When you restore the Hybrid Store data, use the same host name and instance name that were used
when you backed up the data.
For details, see the Hitachi Command Suite Tuning Manager Agent Administration Guide.
(1) Stop Agent services

Use the htmsrv command to stop Agent services.
# Command Line
(2) Execute the htmhsrestore command

The following table lists execution examples of the htmhsrestore command.
# Command Line
2 htmhsrestore -dir /tmp/RAID_backup
(3) Set the environment-dependent information

After executing the htmhsrestore command, see the manual to set the environment-dependent
information, and then make sure that the target is being monitored correctly.

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. Hitachi Storage Command Suite Hitachi Command Suite
. (Abbreviation : HSCS) (Abbreviation : HCS)
2. HiCommand Device Manager Hitachi Device Manager
3. 2 Storage Subsystem Storage System
.
4. 3 Array Group Parity Group
.
5. 4 Host Storage Domain Host Group
. (Abbreviation : HSD)
6. Array Configuration Storage System Configuration

Appendix 9 The policy about the access permission of files and
directories
The file and directory access permission policies are as follows:
(1) Server policy
No. OS Owner Group
1 Solaris root sys or root
2 Linux root root
File and directory access permission policy

- Permissions for files and directories placed or generated by HTnM Server
Only the root user is given write permission.
- HTnM Server-supplied commands
About execution permission of commands, see the manual.
The permission of file and directory that is placed or generated below /opt/jp1pc follows the
Agent policy.
(2) Agent policy

No. OS Owner Group
1 Solaris root sys
2 Linux root sys#1
root#2
3 AIX root system
4 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.

Appendix 10 Cases in which HTnM did not operate normally
10-a Cases in which HTnM did not operate normally due to an incorrect file
In some cases, HTnM does not operate normally because a file with the same name as one
supplied exists in the HTnM (HCS) installation directory.
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 013D93F4 0160877B KATN09921-E EC
com.Hitachi.soft.HiCommand.TM.mc.core.init.InitialUtility#exec() Caused by: java.io.IOException:
CreateProcess: "E:\Program Files\HiCommand\Base\bin\hcmdssrv" /check /server PerformanceReporter
error=193 at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(ProcessImpl.java:81)
at java.lang.ProcessImpl.start(ProcessImpl.java:30) at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at com.Hitachi.soft.HiCommand.TM.mc.util.process.ProcessRunnerImpl.execute(ProcessRunnerImpl.java:88) at
com.Hitachi.soft.HiCommand.TM.mc.util.process.ProcessRunner.executeImpl(ProcessRunner.java:368) 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)

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.

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

Agent is started in AIX. In AIX, the environment variable ODMDIR is specified by
/etc/environment. When Job Management Partner 1/Automatic Job Management System 3
starts a program in AIX, /etc/environment is not inherited. For this reason, if the environment
variable ODMDIR is not explicitly specified, this problem may occur.
10-c.3 Isolating the problem

To isolate the problem, use the AIX ps ewwwg command to check whether the environment
variable ODMDIR is loaded into the RAID Map Agent process jpcagte. The following section
provides an example of how to check the variable.
[Command used]
ps ewwwg
[Output example]
14418032 - A 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.
10-d Unable to launch HiRDB during the establishment of a cluster environment

10-d.1 Problem
HiRDB fails to be launched when establishing a cluster environment and the KFPS01892-E
message is output.
- 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]

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.
The following is an example of this problem:

(1) Install HTnM on the executing node.
(2) Switch the system.
Start/stop the HCS service from the cluster software. (*)
If the HCS service is started (goes online) in an environment in which HTnM is installed
on the executing node but not on the standby node, HiRDB is abnormally terminated.
(3) Install HTnM on the standby node.
Although no details are available without the HTnM installation logs (because they
might have been deleted?), the HBase log shows that HiRDB is running in recovery
mode.
(4) Start/stop HiRDB/ClusterService _HD0.
This stoppage forcibly terminates HiRDB, resulting in the abnormal termination of
HiRDB, similar to (*) above.
10-d.3 Solutions
To recover HiRDB:
(1) Take the HCS service offline from the cluster software.
(2) Move a shared disk onto the executing node.
(3) Change the HiRDB settings.

Change line 13 of the following file as shown below:
<Common-Component-installation-directory>\HDB\CONF\pdsys
from set pd_max_users = 96
to set pd_max_users = 84.

(4) Stop the HiRDB/EmbeddedEdition _HD0 service.
(5) Start the HiRDB/EmbeddedEdition _HD0 service.

To confirm that HiRDB has started:
Wait for a while after starting the service, and then execute the following command to check
whether HiRDB is running:
<Common-Component-installation-directory>\bin\hcmdssrv.exe
/status
(6) Stop HiRDB.

<Common-Component-installation-directory>\bin\hcmdssrv.exe
/stop
(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.
10-e Unable to launch Agent for Platform

10-e.1 Problem
Agent for Platform for AIX fails to start in AIX 5.3 or earlier and the KAVE05033-E message is
output.
- 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.

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.
10-e.3 How to identify the cause of errors

You can check whether the number of bits of the Agent for Platform module is different from
that of the AIX kernel by referring to the following material included in the RAS resources of
Agent for Platform.
[File to check]
localhost/agtu/agent/log/version.log
[Example of the file output]
Build Environment : 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.

Appendix 11 Update of time zone information (HCS 7.0.1 or later)
In Hitachi Command Suite (HCS) version 7.0.1 or later, the JDK DST Timezone Update Tool
(hereafter tzupdater) supplied by Oracle can be used to update the time zone information (all files
under <Suite Install-dir>/jdk/jre/lib/zi, hereafter tzdata) of the common component JDK. This
section describes how to use tzupdater to update time zone information.
This procedure applies to Windows, Linux, and Solaris (SPARC).
It does not apply to Solaris (x64).
11-a Obtaining tzupdater

Download tzupdater from the Oracle download site.
As of 2011/3/9, its URL is as follows:

URL: http://www.oracle.com/technetwork/java/javase/downloads/index.html
(Oracle Technology Network > Java > Java SE > Downloads)
[Java SE Downloads]
-[Additional Resources]
-[JDK DST Timezone Update Tool - 1.3.xx](*)
(*) xx in 1.3.xx indicates the version number of tzupdater.
11-b Using tzupdater

(1) Checking the tzdata versions
Use the following command to check the versions of tzdata for the current Hitachi JDK and for
tzupdater.
- tzdata version check command
For Windows
<Suite Install-dir>\jdk\bin\java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar -V
<Suite Install-dir>\uCPSB\jdk\bin\java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar
-V
For Solaris
<Suite Install-dir>/jdk/bin/java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar -V
For Linux
<Suite Install-dir>/jdk/bin/java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar -V
<Suite Install-dir>/uCPSB/jdk/bin/java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar
-V
-Output example

For Windows
"C:\Program Files\HiCommand\Base\jdk\bin\java" -Djava.vendor="Sun Microsystems Inc." -jar
"C:\Program Files\HiCommand\Base\tzupdater.jar" -V
tzupdater version 1.3.29-b01 ------ tzupdater tool version
JRE time zone data version: tzdata2007g ------ Current tzdata version
Embedded time zone data version: tzdata2010f ------ Updated tzdata version
For Solaris, Linux
% /opt/HiCommand/Base/jdk/bin/java -Djava.vendor="Sun Microsystems Inc." -jar
/tmp/tzupdater.jar -V
For Windows
"C:\Program Files\HiCommand\Base64\uCPSB\jdk\bin\java"
-Djava.vendor="Sun Microsystems Inc." -jar "C:\Program
Files\HiCommand\Base64\tzupdater.jar" -V
JRE time zone data version: tzdata2013d ------ Current tzdata version
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
(2) Updating tzdata

Use the following command to update tzdata for the current Hitachi JDK.
- tzdata update command
For Windows
<Suite Install-dir>\jdk\bin\java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar -v -u
<Suite Install-dir>\uCPSB\jdk\bin\java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar
-v -u
For Solaris
<Suite Install-dir>/jdk/bin/java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar -v -u
For Linux
<Suite Install-dir>/jdk/bin/java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar -v -u
<Suite Install-dir>/uCPSB/jdk/bin/java -Djava.vendor="Sun Microsystems Inc." -jar tzupdater.jar
-v -u
-Output example
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. ------Vendor name specified in the command line
java.version: 1.5.0_11 ------JDK version
Extracting files... done.
Renaming directories... done.
Validating the new time zone data... done.
Time zone data update is complete.
For Solaris :
# /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
Validating 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.

For Linux
/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
For Windows
"C:\Program Files\HiCommand\Base64\uCPSB\jdk\bin\java"
-Djava.vendor="Sun 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
For Linux
/opt/HiCommand/Base64/uCPSB/jdk/bin/java -Djava.vendor="Sun Microsystems Inc."
-jar "/tmp/tzupdater.jar" -v -u
java.home: /opt/HiCommand/Base64/uCPSB/jdk/jre ------JDK to be applied

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.

Appendix 12 Actions to be taken when memory is insufficient
12-a Actions to be taken when the jpcrpt command is unable to output information
because of insufficient memory
12-a.1 Cases
When the jpcrpt command is executed from the command line, the following message is
output, and a report cannot be output.
Case 1:
KAVJK0405-E jpcrpt -y -input E:\Monthly_Stats\Graphical\Input_Files\PP2USP06O_LDev_LDS1.xml -o
E:\Monthly_Stats\Graphical\Results\PP2USP06O\PP2USP06O_LDev_Response_4000_to_7FFF: A Manager
access error occurred. Maintenance information: ViewServer error code: -2001 Make sure communication with
the Manager host can be performed correctly, and that the Manager is running.
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
- In Ver.7
- In Ver.8
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.

< jpcrpt_logX.log >
nnnn 20YY/MM/DD hh:mm:ss.xxx HTM-PR 000023F4 000022C8 KAVJZ5999-E EC
[PR0111:EC :10] Exception
java.lang.OutOfMemoryError: Java heap space
nnnn 20YY/MM/DD hh:mm:ss.xxx HTM-PR 000023F4 000022C8 KAVJZ5999-E EC

[PR0112:EC :10] Exception
java.lang.OutOfMemoryError: Java heap space
nnnn 20YY/MM/DD hh:mm:ss.xxx HTM-PR 000023F4 000022C8 KAVJK0401-E

[PR0113:INF:10] jpcrpt -y -input E:\Monthly_Stats\Graphical\Input_Files\PP3USP01O_LDev_LDS1.xml -o
E:\Monthly_Stats\Graphical\Results\PP3USP01O\PP3USP01O_LDev_Response_4000_to_7FFF: 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
- In Ver.7
- In Ver.8
(2) Increase the size of available View Server memory

For details about how to set the size of available View Server memory, see the following
manual:
- In Ver.6
- In Ver.7
- In Ver.8
(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

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.
[HCS-installation-directory\Base\CC\web\containers\TuningManager\logs\javalogXX.log]
[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: 20018K->19993K(21824K)][Tenured:
436928K->436928K(436928K)][Perm: 55905K->55884K(65536K)][cause:ObjAllocFail][User: 2.8281250
secs][Sys: 0.0000000 secs]
[OOM][Thread: 0x056312c0]<Wed Jun 30 12:05:10.283 2010>[java.lang.OutOfMemoryError : requested 6520848
bytes. (Java Heap) : 62 threads exist] [
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.

(2) Specify a longer interval between the scheduled polling times.
(3) Use multiple HTnM hosts to reduce the number of Agents monitored by one HTnM host.

Appendix 13 Recommended action when the KAVE00213-W message is
output and when performance data collection is skipped
When the KAVE00213-W message is output, see the section Message KAVE00213-W is output
to the common message log of the following manual to take action accordingly:
- In Ver.6
- In Ver.7
- In Ver.8
As supplementary information to the above-mentioned manual, this document explains the

procedure used to identify the target for which the KAVE00213-W message is issued in the log and
provides a guide for specifying a value for the Collection Interval for a record of the PI record type.
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.
1) Identifying the PID and record type

In the jpclog, check the output content of the KAVE00213-W message. For details about the
output format of the jpclog, see the Log Information Analysis Guide.
- Output time and date
- PID
- Record type
Output example of jpclog

2012/04/18 17:01:15 jpcagtd 00006140 00004964 cnsrnode.cpp 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)
2) Identifying the Agent instance

Identify the Agent instance that corresponds to the PID confirmed in 1).
Check the msglogX of each Agent instance and look for an msglog that was output in the
time period checked in 1) and that includes the same PID checked in 1), in order to identify the
corresponding Agent instance. As the output destination directory of msglog differs for each

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.
Output example of msglogX:

Output destination of msglogX: /opt/jp1pc/agtd/agent/HKVSP/log/msglog1
2012/04/18 17:01:15 jpcagtd 00006140 00004964 RecordBuilder.c 1819 I Exited the function
(HpmRL_GetRaidInf). (rc=0)(Instance count : PORT=64, LDEV=2062, PDEV=0, RAIDG=201, LUSE=53,
ExLDEV=151, CLPR=4, PROC=32, VVOL=1158, POOL=10, VVOL(HDT)=0, POOL(HDT)=0, LDS1)
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.
Considerations for changing the Collection Interval

- The time required for data collection varies depending on the configuration of the target being
monitored and the network status. Therefore, set a value with a margin large enough for the
Collection Interval.
- Do not specify a collection interval exceeding 3,600.
- For the Collection Interval, specify a specifiable value defined for each record. If you specify a
value other than a value defined for each record, the performance data might not be correctly
stored. For details about the specifiable values defined for each record, see the explanation of the
respective records in the manual.
13-b.1 Agent for RAID

For the Collection Interval for records of the PI record type for Agent for RAID, specify a value
larger than the time required for collecting the configuration information.
You can obtain the time required for collecting configuration information either from the
collection time (COLLECTION_TIME) field of a record of the PD record type or from the log.
To obtain the value from the log, check the msglogX of the Agent instance that you identified in
13-a and calculate the difference of the output times of the following log items:
- Start the function (HpmRL_GetRaidInf)
- Exited the function (HpmRL_GetRaidInf)

Example of how to obtain the value from the log:
The following example shows that it took 1 minute and 15 seconds to collect PD records.
2012/04/18 17:00:00 jpcagtd 00006140 00004964 RecordBuilder.c 1008 I Display the RecordType ( PD PD_LDC
PD_PTC PD_LSEC PD_RGC PD_ELC PD_CLPC PD_PLTC PD_PLTS PD_VVTC PI_LDS PI_LDS1 PI_LDS2
PI_LDS3 PI_LDE PI_LDE1 PI_LDE2 PI_LDE3 PI_LDA PI_PDS PI_RGS PI_PDOS PI_PLS PI PI_PTS PI_CLPS
PI_PRCS PI_CLCS ).
2012/04/18 17:00:00 jpcagtd 00006140 00004964 RecordBuilder.c 1758 I Start the function
(HpmRL_GetRaidInf). (arg1=261599, arg2=\\.\PhysicalDrive1, arg3=2, arg4=, arg5=, arg6=cbe5c8, arg7=0,
arg8=cce01c)
2012/04/18 17:01:15 jpcagtd 00006140 00004964 RecordBuilder.c 1819 I Exited the function
(HpmRL_GetRaidInf). (rc=0)(Instance count : PORT=64, LDEV=2062, PDEV=0, RAIDG=201, LUSE=53,
ExLDEV=151, CLPR=4, PROC=32, VVOL=1158, POOL=10, VVOL(HDT)=0, POOL(HDT)=0, LDS1)
13-b.2 Agent for SAN Switch

This section explains how to calculate a guide value for the Collection Interval for PI records in
Agent for SAN Switch.
1) Obtaining the recommended value from the fabric configuration

For details about the recommended values of the Collection Interval for each fabric configuration
(number of ports), see the section Agent for SAN Switch of Notes on Collecting Records of the
following manual:
- 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
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 I Return the java
function(method=enumerateInstances, detail1=Brocade_SANActiveConnection(*1), detail2=537)
*1: The output information differs depending on the destination to which the instance is connected. For details on the
information that is output, see the following table.
# Destination to which the instance is connected Output content of msglogX
1 Brocade(Network Advisor SMI Agent / DCFM SMI Agent) Brocade_SANActiveConnection
2 Brocade(SMI Agent for FOS)
3 Brocade(SMI Agent for EOS) McDATA_SwitchActiveConnection
4 Cisco(DCNM-SAN SMI-S Agent) CISCO_ActiveConnection
5 Cisco(Seed Switch)

2) Obtaining the recommended value from the log
If you still continue to encounter the KAVE00213-W message even after setting the recommended
value for the Collection Interval in 1), set a collection interval larger than the time required for
collecting data. The time required for data collection is the sum of the time for collecting
configuration information and the time for linking to the collected configuration information. You
can check the time required for collecting configuration information and the time required for
linking to the collected configuration in msglogX.
2012/02/10 08:30:00 jpcagtw 00006548 00007024 RecordBuilder.c 0261 I Display the RecordType ( PI PI_PTS
PI_PTES PI_SWS PI_SWES ).
(Omitted)...(Time required for collecting configuration information: 8 min [08:30:00 - 08:37:54])
2012/02/10 08:37:54 jpcagtw 00006548 00007024 saC_CimData.cpp 0264 I Return the java
function(method=enumerateInstances, detail1=CISCO_DeviceSAPImplementation(*1), detail2=3286)
(Omitted)...(Time required for linking to configuration information: 35 min [08:37:54 - 09:12:38])
2012/02/10 09:12:38 jpcagtw 00006548 00007024 saC_SwitchAcces 0534 I Exit the function
(saC_SwitchAccessorCI(*2)::RefreshAllObject). (rc=0)
*1 and *2: The output information differs depending on the destination to which the instance is connected. For
details on the information that is output, see the following table.
# (*1)/(*2) Destination to which the instance is Output content of msglogX
connected
1 (*1) Brocade(Network Advisor SMI Agent / Brocade_SwitchFCPortOfEthernetPort

DCFM SMI Agent)
2 Brocade(SMI Agent for FOS) Brocade_SwitchFCPortSCSIProtocolEndPoint
3 Brocade(SMI Agent for EOS) McDATA_FabricPortGroup
4 Cisco(DCNM-SAN SMI-S Agent) CISCO_LogicalForPhysicalComputerSystem
5 Cisco(Seed Switch) CISCO_DeviceSAPImplementation
6 (*2) Brocade(Network Advisor SMI Agent / saC_SwitchAccessorDCFM

DCFM SMI Agent)
7 Brocade(SMI Agent for FOS) saC_SwitchAccessorBR
8 Brocade(SMI Agent for EOS) saC_SwitchAccessorMC
9 Cisco(DCNM-SAN SMI-S Agent) saC_SwitchAccessorDCNM
10 Cisco(Seed Switch) saC_SwitchAccessorCI

Appendix 14 Service IDs and service keys of the products
14-a Service IDs and service keys specified when backing up and restoring the StoreDB
The table below shows the correspondence relationship between the service IDs and service keys of
the products (services) specified when backing up and restoring the StoreDB.
Table14.a.1-1 Service IDs and service keys specified when performing backup and restore
operations
# Product Service ID Service key
1 Collection Manager PSxxxx mgr

2 RAID Agent DSxxxx agtd
3 RAID Map Agent ESxxxx agte
4 EAP Agent MSxxxx agtm
5 NAS Agent NSxxxx agtn
6 Oracle Agent OSxxxx agto
7 SQL Agent QSxxxx agtq

8 DB2 Agent RSxxxx agtr
9 Platform Agent (Windows) TSxxxx agtt
10 Platform Agent (Unix) USxxxx agtu
11 Switch Agent WSxxxx agtw
12 Exchange Agent ZSxxxx agtz
13 Action Handler - act
14 Status Server - stat
15 Health Check Agent 0Sxxxx agt0
Note: xxxx indicates an arbitrary string.

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
- In Ver.7
- In Ver.8
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
- In Ver.7
- In Ver.8
(2) Stop the services on the HTnM agents host.

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.

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.
(3) Stop the services on the HTnM server host.

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.
(4) Check the currently configured physical host name.

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. If the acquisition method is hostname mode:
hostname
2. If the acquisition method is uname mode:
uname -n
(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
changed host name can be resolved in the Tuning Manager system.
(7) If necessary, perform HTnM agent-specific procedures.

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.

(8) Start the services on the HTnM server host.
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.
(9) Cancel the health check agent settings.

Use Performance Reporter to remove the alarm table mapping for the health check agent whose
service ID includes the old host name.
(10) 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 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. Delete the remaining service information.

Execute the following command to delete the remaining service information:
jpcctrl delete "*" host=< the old 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.
jpcctrl delete "*" host=< the old host name > -force
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 >

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.
Check the output of the above two commands to confirm that no entries have the old host
name in the Service ID column.
(12) Apply the HTnM server service information.

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.
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 >
(14) Start the services on the HTnM agents host.

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.
use the cluster software to start the HTnM agents services.
(15) Respecify the health check agent settings.

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).
(16) Respecify the HTnM agent settings.

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

(17) Update the alarm settings.
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.
(18) Perform checks after changing the settings.

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
Manager server in the following manual:
- In Ver.6
- In Ver.7
- In Ver.8
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.
(2) Stop the services on the HTnM agents host.

Stop all HTnM agents programs and services on the HTnM agents host. Use the 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.
(3) Check the currently configured physical host name.

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. If the acquisition method is hostname mode:
hostname
2. If the acquisition method is uname mode:
uname -n
(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
changed host name can be resolved in the Tuning Manager system.
(6) If necessary, perform HTnM agent-specific procedures.

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

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. 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. Delete the remaining service information.

Execute the following command to delete the remaining service information:
jpcctrl delete "*" host=< the old host name >
or
jpcctrl delete "*" host=< the old host name > lhost=< the logical host name of the HTnM
server host >
jpcctrl delete "*" host=< the old host name > -force
or
jpcctrl delete "*" host=< the old host name > lhost=< the logical host name of the HTnM
server host > -force
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 >
or
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 >

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.
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.
(8) Apply the HTnM server service information.

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.
(9) Start the services on the HTnM agents host.

Start the HTnM agents programs and services. Use the jpcstart command to start the services.
(10) Respecify the HTnM agent settings.

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).
(11) Update the alarm settings.

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.

(12) Perform checks after changing the settings.
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.

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) .
What is the value of Get 2

Host Mode (a)?
0 or 1
In the hostname.txt file, check the

physical host name (c) (*1).
Are (b) and (c) the

same? 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 Value of Procedure
Get Host Mode
1 Windows 0 or 1 Check the contents of the hostname.txt file, which contains only
host names.
2 UNIX 0 In the hostname.txt file, in the output of the uname command,
check the name of the host.
3 1 In the hostname.txt file, in the output of the hostname
command, check the name of the host.

Appendix 16 Initializing the database (V8.0.1 or later)
If a database failure occurs during operation, recover the database by restoring it with the
hcmds64db command or by importing it with the hcmds64dbtrans command.
If the database cannot be recovered, forcibly delete it, and then create it again to initialize it.
For details about how to initialize the database, see Hitachi Command Suite Software
Troubleshooting Guide.
Appendix 17 Steps in a cluster environment without using commands

In HTnM server V8.1.2 or later, support for the following commands improved some existing steps
in a cluster environment:
- hcmds64clustersrvupdate
- hcmds64clustersrvstate
If you need to perform the steps in a cluster environment without using the above commands, see the
"Hitachi Command Suite Software Troubleshooting Guide".

Appendix 18 Precautions when using Hybrid Store (Version 8.1.3 or later)
18-a Procedure to change the data storage format from Hybrid Store to Store database
The process to change the data storage format of the RAID Agent and NAS Agent being operated
is not publicly available to users. However, if you need to change the data storage format from
Hybrid Store to Store database to avoid an error, see the procedure below.
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.
Table 18-a-1 Possibility of data storage format change

# Data storage format of Agent whose Changed data storage format Possibility Procedure for
installed agent data storage of change change
-: Not installed
format is to be
-: Not installed P: Possible
changed
I:Impossible
RAID Agent NAS Agent RAID Agent NAS Agent
1 Hybrid Store Hybrid Store RAID Agent StoreDB StoreDB P Procedure A

NAS Agent
2 Hybrid Store Hybrid Store RAID Agent StoreDB Hybrid Store I -
3 Hybrid Store Hybrid Store NAS Agent Hybrid Store StoreDB P Procedure B
4 Hybrid Store Store DB RAID Agent StoreDB StoreDB P Procedure A
5 Hybrid Store - RAID Agent StoreDB - P Procedure A
6 Store DB Hybrid Store NAS Agent StoreDB StoreDB P Procedure A
7 - Hybrid Store NAS Agent - StoreDB P 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:
htmsrv stop -all
(2) Modify the data_file_manage.ini property file.

- Location where the files are stored
For Windows:

<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
(3) Modify the usrconf.cfg property file.

For Windows:
<installation-folder>\htnm\HBasePSB\CC\server\usrconf\ejb\AgentRESTService\usrconf.cfg
For UNIX:
/opt/jp1pc/htnm/HBasePSB/CC/server/usrconf/ejb/AgentRESTService/usrconf.cfg
- Modification
add.jvm.arg=-Xmx6144m
add.jvm.arg=-Xmx1024m
(4) Delete the migration_status.ini property file.

If the migration_status.ini file exists, delete it. Repeat this step for each type of
Agent.
For Windows:
<installation-folder>\agtX\ migration_status.ini
For UNIX:
/opt/jp1pc/agtX/migration_status.ini
(5) Rename the property file support_switch_db.ini to

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.

For Windows:
<installation-folder>\agtX\support_switch_db.ini
For UNIX:
/opt/jp1pc/agtX/support_switch_db.ini
(6) Delete the dbmigrating.dat file.

If the dbmigrating.dat file exists, delete it. Repeat this step for each type of Agent.
For Windows:
<installation-folder>\agtX\agent\dbmigrating.dat
For UNIX:
/opt/jp1pc/agtX/agent/dbmigrating.dat
(7) Delete all Hybrid Store data.

If you changed the default storage location of the data, see the
dbdataglobalconfig.ini and dbconfig.ini property files to check the location.
For details on these property files, see the Hitachi Command Suite Tuning Manager Agent
Administration Guide.
(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
(9) Execute the following htmsrv command to start all services:

htmsrv start -all
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:
htmsrv stop -all

Agent.

For Windows:
For UNIX:

For Windows:
For UNIX:

For Windows:
For UNIX:

(6) Execute the following htmsrv command to start all services:

htmsrv start -all
Procedure C:
If only NAS Agent is installed, follow the steps below:
htmsrv stop -all

(2) Modify the data_file_manage.ini property file.
For Windows:
<installation-folder>\htnm\agent\system\data_file_manage.ini
For UNIX:
/opt/jp1pc/htnm/agent/system/data_file_manage.ini
- Modification
[Mode]
[Mode]
Database Type=Store

Agent.
For Windows:
For UNIX:

For Windows:
For UNIX:


For Windows:
For UNIX:

(7) Execute htmrestctrl command to disable the Tuning Manager API.

htmrestctrl off
(8) Execute the following jpcstart command to start all services:

jpcstart all

Appendix 19 How to check the data storage format of Agent
The following Agents can use two data storage formats, the Store database and the Hybrid Store.
- RAID Agent 8.1.3-00 or later
- NAS Agent 8.2.1-00 or later
This chapter explains how to check the data storage format of the above Agents by using RAS
materials.
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 Database Type value of support_switch_db.ini Data storage format
data_file_manage.ini
1 ScalableDB Hybrid Store

2 ScalableDB Store database
3 Store Store database
5 (Empty string) Store database#1
6 (Empty string) Store database
7 - Store database
8 - Store database
[Legend] : File exists : File does not exist
#1: Currently migrating to Hybrid Store, or was terminated abnormally during the migration.
[Location of the data_file_manage.ini file]

<directory-to-extract-RAS-file>\localhost\htnm\agent\system\data_file_manage.ini
[Definition example of data_file_manage.ini]

[Mode]
[Location of the support_switch_db.ini file]

<directory-to-extract-RAS-file>\agtd.agtras\<host-name>\agtd\support_switch_db.ini

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 Database Type value of support_switc dbmigrating.dat Data storage format
nage.ini data_file_manage.ini h_db.ini

1 ScalableDB Store database#1
2 ScalableDB Hybrid Store
3 ScalableDB Store database#1
4 ScalableDB Store database
5 Store Store database#1
7 Store Store database#1
10 (Empty string) Hybrid Store
12 (Empty string) Store database
13 - Store database#1
14 - Store database
15 - Store database
16 - Store database
[Legend] : File exists : File does not exist
#1: Currently migrating to Hybrid Store, or was terminated abnormally during the migration.
[Location of the data_file_manage.ini file]

<directory-to-extract-RAS-file>\localhost\htnm\agent\system\data_file_manage.ini
[Definition example of data_file_manage.ini]

[Mode]

[Location of the support_switch_db.ini file]
<directory-to-extract-RAS-file>\agtX.agtras\<host-name>\agtX\support_switch_db.ini
[Location of the dbmigrating.dat file]

<directory-to-extract-RAS-file>\agtX.agtras\<host-name>\agtX\agent\dbmigrating.dat
-End of document-

Hitachi Tuning Manager: Troubleshooting Guide 08-40-00 Rev01 2016/2/1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hitachi Tuning Manager: Troubleshooting Guide 08-40-00 Rev01 2016/2/1

Uploaded by

Copyright:

Available Formats

FE-94HC095-41

Hitachi Tuning Manager

1 Hitachi Proprietary Information

(b) Using a script to execute a command provided by the product

(c) Substituting terms when using this document

2 Hitachi Proprietary Information

3 Hitachi Proprietary Information

4 Hitachi Proprietary Information

Hitachi Tuning Manager Agent for Network Attached Storage

Hitachi Tuning Manager Agent for Oracle

Hitachi Tuning Manager Agent for Platform (for UNIX systems)

Hitachi Tuning Manager Agent for Platform (for Windows systems)

Hitachi Tuning Manager Agent for RAID

Hitachi Tuning Manager Agent for RAID Map

Hitachi Tuning Manager Agent for Microsoft SQL Server

Hitachi Tuning Manager Agent for Microsoft Exchange Server

Hitachi Tuning Manager Agent for SAN Switch

Hitachi Tuning Manager Agent for IBM DB2 (*1)

Hitachi Tuning Manager Agent for HealthCheck

Hitachi Tuning Manager Agent for Enterprise Applications (Supported

Hitachi Tuning Manager - Agent for IBM DB2 Universal Database

Collection Manager Hitachi Tuning Manager Collection Manager

DB2 Agent In Ver.6 to 7.4

Hitachi Tuning Manager Agent for IBM DB2 Universal Database

Hitachi Tuning Manager - Agent for IBM DB2

Main Console Hitachi Tuning Manager Main Console

Oracle Agent Hitachi Tuning Manager Agent for Oracle

Performance Reporter Hitachi Tuning Manager Performance Reporter

RAID Agent Hitachi Tuning Manager Agent for RAID

5 Hitachi Proprietary Information

EAP Agent Hitachi Tuning Manager Agent for Enterprise Applications

Tuning Manager server A generic name for:

# Hitachi Tuning Manager Collection Manager

# Hitachi Tuning Manager Main Console

# Hitachi Tuning Manager Performance Reporter

HealthCheck Agent Hitachi Tuning Manager Agent for HealthCheck

OCI Oracle Call Interface

ADO ActiveX Data Object

Tuning Manager REST HCS Tuning Manager REST Application Service

or HTnM REST Application

HTnMAgent REST Tuning Manager - Agent REST Application Service

HTnM-Agent REST Tuning Manager - Agent REST Web Service

HTnM-Agent REST Services A generic name for:

Tuning Manager - Agent REST Application Service

Tuning Manager - Agent REST Web Service

6 Hitachi Proprietary Information

CLI Command Line Interface

CLPR Cache Logical PaRtition

CRC Cyclic Redundancy Check

DAMP2 Disc Array Management Program 2

DHCP Dynamic Host Configuration Protocol

DLL Dynamic Linking Library

DNS Domain Name System

EFCM Enterprise Fabric Connectivity Manager

FQDN Fully Qualified Domain Name

GBIC Gigabit Interface Converter

HBA Host Bus Adapter

HDT Hitachi Dynamic Tiering

HDU Hard Disk Unit

HTnM Hitachi Tuning Manager

HTM Hitachi Tuning Manager

HTML Hyper Text Markup Language

Ipv4 Internet Protocol Version 4