Академический Документы
Профессиональный Документы
Культура Документы
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.
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).
(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
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:
In Ver.7.4.1 or later
Exchange Agent Hitachi Tuning Manager Agent for Microsoft Exchange Server
Agent for Server System Hitachi Tuning Manager Agent for Server System
NAS Agent Hitachi Tuning Manager Agent for Network Attached Storage
Platform Agent(Unix) Hitachi Tuning Manager Agent for Platform (for UNIX systems)
Platform Agent(Windows) Hitachi Tuning Manager Agent for Platform (for Windows systems)
or PR
RAID Map Agent Hitachi Tuning Manager Agent for RAID Map
SQL Agent Hitachi Tuning Manager Agent for Microsoft SQL Server
# Hitachi Tuning Manager Tuning Service (In Ver.6.0 to earlier than 8.0)
Application Service
Service
Application Service
Web Service
HA High Availability
I/O Input/Output
IP Internet Protocol
OS Operating System
SP Service Pack
TBD To Be Determined
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.
Appendix 6 For the HPE OEM version, substitute the following terms as indicated ............................... 370
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 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 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
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
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
No
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.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
#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
Hitachi Command Suite Tuning Manager Software Installation Guide
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.
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.)
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.
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 >
If installation of Tuning Manager fails, check if the KATN00326-W message is output in the trace
log file for installation, and in this case, perform the following procedure. When the KATN00326-W
message is output for hcmdssrv, perform the force uninstall of Tuning Manager server, and install
Hitachi Command Suite products including Tuning Manager server.
[Message]
KATN00326-W The following invalid empty files were detected at the installation destination of
Common Component:
< The name of Common Component command file detected zero byte >
Confirm the version of the Common Component on the integrated installation media .#2
No
Is the stop of services succeeded? #5
Yes
No
Perform the force uninstall of the Tuning
Success?#7
Manager server.#8
Yes
#1 How to confirm the version of the Common Component that have been installed
[In Ver.7.4.1 to earlier than 8.0.0]
- In Windows
Confirm the version by the key (a 6-digit numeric value) under the registry key shown below
indicating the version, revision, and fixed number.
<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
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
(Example)
In the case when the version of the Common Component on the integrated installation media is
V7.5.0
cat BUILD
07500000
Note: Check high 6 digit numeric value which shows the version, revision, and fixed number and
ignore 7, 8 digit numeric value.
#3 Confirm the result of version check at #1 and #2, and the numbers of high 6 digit numeric value
are identical.
Note: High 6 digit numeric value shows the version, revision, and fixed number and ignore 7, 8
digit numeric value.
- In Solaris,Linux
< Install directory of Common Component >/bin/hcmdssrv -stop
- In Solaris,Linux
< Install directory of Common Component >/bin/hcmds64srv -stop
- In Solaris,Linux
Refer to "3-c.5.6 Stop the service of HiRDB"
- In Linux
Refer to "3-i.5.6 Forcibly Stopping the HiRDB Process"
- In Solaris,Linux
<Common-Component-installation-directory>/bin/hcmdssrv -statusall
- In Solaris,Linux
<Common-Component-installation-directory>/bin/hcmds64srv -statusall
#6 When executing the force installation of Common Component, move your current directory to the
stored directory of Common Component on the integrated installation media which is shown above
and execute it by the command as below.
- In Windows
- In Solaris
- In Linux
(*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
#7 Check if the result of the forced installation of Common Component in the following way.
[In Ver.7.4.1 to earlier than 8.0.0]
-In Windows
Check if the exit code is zero by referring to a value of the registry below.
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 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
Installation of Agent
Yes
Did an error occur during
installation of the Agent?
No
Yes Has Tuning Manager series
#7
been already installed ?
Perform Check K#13. Yes
No
Did an error occur during
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
END
#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.
#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.
In Ver.8.0.0 or later
Hitachi Command Suite Tuning ManagerInstallation
Guide
Changing a host name after starting operations
If the error message above has been output, change the port number used by other process. If you want to use the Agent without changing the port number
used in other process; stop the corresponding process, reinstall the Agent and then change the port number for the Agent(*1)(*2).
(*1) For instructions of changing port number, refer the following manual.
Hitachi Command Suite Tuning Manager Installation Guide
Configuring the port number
(*2) If this Check corresponded in VUP installation and then reinstallation was performed, the installation type displayed in the installer dialog will be
"Overwrite".
#11 Check I (Confirmation of IPv4 communication) (Agent for RAID V8.0.0 or later)
If the IPv4 communication is not configured in the installation target host, installation will fail.
Check if any of the following conditions meet:
(1) The network interface in operation does not exist.
(2) IPv4 address is not set in the network interface.
Note:
Even in Linux (x64), some of the prerequisite packages must be the 32-bit versions. These prerequisite packages might also have
64-bit versions under similar names. Check carefully to make sure that the 32-bit packages are installed rather than the 64-bit
versions.
#13 Check K (verification of the status of Hybrid Store) (Agent for RAID v8.1.3 or later, Agent for NAS v8.2.1 or later)
When the installation finishes, one of the following warning messages is displayed to prompt you to perform the settings to convert to
Hybrid Store databases.
(1) The conversion to Hybrid Store databases did not finishe. After the installation finishes, perform the settings to convert to Hybrid
Store databases, and then start operation.
(2) An attempt to convert to Hybrid Store databases failed. After the installation finishes, follow the action to be taken when the
htmhsmigrate command fails, and then perform the settings to convert to Hybrid Store databases. <command=htmhsmigrate,
rc=command-return-value>
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.
No
Could you log in to the
Tuning Manager server?
No
Yes Are Checks H#10
and I#11 applicable?
No
END
Figure 2.3.2-1 Error during startup of a Tuning Manager server service flow
Note that some Agents stop the service if an attempt to check the connection with the
monitoring target resource has failed during startup of the service.
target) Resource type Data collection method collect data from the monitoring target
has failed
started
RAID Map Agent Server & OS commands, Standard Inquiry, In-band -- Continues the
so on
HUS100)
Switch Agent Brocade switch In Ver.7.1 to 7.6.1: Out-band Fails to start the
(M-Model)
(Brocade API)
In Ver.6.1 to 7.0:
Windows/Solaris: SMI-S
Switch Agent Brocade switch In Ver.7.1 to 7.6.1: Out-band Fails to start the
Switch Agent Brocade switch In.Ver.6.0 to 6.1: Out-band Fails to start the
In Ver.6.2 to 7.0:
Windows/Solaris: SMI-S
Switch Agent Brocade switch In Ver.7.1 to 7.6.1: Out-band Fails to start the
Windows/Solaris: SMI-S
Switch Agent CISCO switch In Ver.7.1 to 7.6.1: Out-band Fails to start the
Windows/Linux: SMI-S
Switch Agent CISCO switch In Ver.7.2.1 to 7.6.1: Out-band Fails to start the
2.3.3.1.6.
2.3.3.1.7.
2.3.3.1.8.
Exchange Agent Exchange Win API, Performance DLL -- Fails to start the
2.3.3.1.9.
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.
Make sure that the services for DCFM and DCFM SMI
Yes End Agent are running.
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.
Yes
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.
Yes
2
No
Is Agent common check#1
applicable?
Yes
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
displaying information on
the monitored switches? #5
Figure 2.3.3.1.2-1 Error during startup of the Switch Agent service flow
(when using Brocade instances (7.0 or earlier) or Brocade (SMI Agent for FOS) instances (7.1 or
later) to monitor Brocade B-Model switches)
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.
Did the service No Note: Bridge Agent only supports Switch Agent
version 6.1 or earlier.
fail to start?
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
displaying information on
the monitored switches? #8
Figure 2.3.3.1.3-1 Error during startup of the Switch Agent service flow
(when using McDATA instances (7.0 or earlier) or Brocade (SMI Agent for EOS) instances (7.1 or later)
to monitor Brocade M-Model switches)
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.
Make sure that HTM-Server is installed on the server
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.
Figure 2.3.3.1.4-1 Error during startup of the Switch Agent service flow
when using CISCO instances (7.0 or earlier) or CISCO (Seed Switch) instances (7.1 or later) to monitor
Cisco switches)
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?
Figure 2.3.3.1.5-1 Error during startup of the Switch Agent service flow
when using CISCO(DCNM-SAN SMI-S Agent) instances (7.2.1 or later) to monitor Cisco switches)
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.
Start of the service
Yes
Figure 2.3.3.1.6-1 Error during startup of the Oracle Agent service flow
Yes
END
Figure 2.3.3.1.7-1 Error during startup of the SQL Agent service flow
END
Figure 2.3.3.1.8-1 Error during startup of the DB2 Agent service flow
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Yes Exchange\Setup
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
maintenance information.
For details about how to use the jpcras command, see
4.1.5. jpcras command.
END
No
Did the service
fail to start?
Yes
Figure 2.3.3.1.9-1 Error during startup of the Exchange Agent service flow
Yes
Yes
Did the service fail
to start?
END
Contact the support center and ask
for investigation.
Figure 2.3.3.3-1 Error during connection between Collection Manager and Agent flow
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
(#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
Yes
Can you connect to
Tuning Manager Server? (# 1)
Figure 2.3.4-2 Connection to Tuning Manager REST Service from client API flow
#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.
No
Collect the logs#10.
See 2.3.3.3.
#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.
Yes
Is polling to
Agent#6 successful?
No Is Check D#7 No
applicable?
Are Check E#8 Yes
applicable? Yes
Figure 2.4-1 Tuning Manager server error causing n/a display for data flow
Refresh button
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.
recorded appears.
Figure 2.4.2.3-2: Checking the Last Recorded Time in the Polling Details window
2 The Agent Collector service is running, but has failed to collect data from the See 2.4.5.2.
server runs.
2 The service of Agent Store stopped during the period of time for See 2.3.3.2.
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
KAVE00166-W message is
output to a log. To
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
Method:
Use PR to display the Agent history data for instance Brocade A.
Data for the number of bytes received at the switch is stored in the following records:
- Configuration information for the port: Switch Agent/PD_SWS record
Create and display a report showing the history data for the PD_SWS record.
Result:
The history report does not contain the data of the period of time from 13:00 in December 7,
2004 to 08:00 in December 8, 2004. The report contains data earlier than 13:00 in December 7,
2004 or later than 08:00 in December 8, 2004.
Error isolation:
An error shown in No. 2 or 3 in Table 2.4.4.2-1 may have occurred.
Agent operates depending on the system clock of the host on which it is installed. If the system
clock of the machine containing Agent is behind the system clock of the machine running Tuning
Manager server, data collection from Agent may delay during the specified polling time.
The following example shows the case where Main Console does not display the Agent data
because the system clock of the host running Agent is behind the system clock of the host running
Tuning Manager server.
Example:
Conditions:
Tuning Manager products running on host A: Tuning Manager server and Agent A
System clock of host A: 2004/12/08 13:00
Tuning Manager server on host A has been running from 11:50 in December 8, 2004.
In host A, the scheduled polling is set to 13:00 and 14:00 in Main Console.
Polling results:
Tuning Manager server performed the first polling when the system clock of host A reached
2004/12/08 13:00.
After the polling finished, Main Console displayed data of Agent A running on host A, but
The second polling collected the following records from the Agents:
Host A: Records at 2004/12/08 12:00 (Data aggregation for the PI-type record completed.)
Records at 2004/12/08 13:00 (Data aggregation for the PI-type record completed.)
Records at 2004/12/08 14:00 (Data aggregation for the PI-type record is
incomplete.)
Host B: A record of 2004/12/08 12:00 (Data aggregation for the PI-type record
completed.)
Records at 2004/12/08 13:00 (Data aggregation for the PI-type record is
incomplete.)
Note: Since the host B clock did not reach 14:00 at the second polling, a record of
14:00 did not exit in Agent Store.
As a result, the records at 2004/12/08 13:00 collected from Agent A on host A and the
records at 2004/12/08 12:00 collected from Agent B on host B are stored in InterBase or
HiRDB during the second polling.
For an error in the Agent for the logical host in a cluster configuration, collect the following
information:
(10) Information about the cluster software
When the cluster software is used to start or stop Agent, or to perform a failover, information
about the cluster software is needed to identify where (cluster software or Agent) the error
occurred.
75 Hitachi Proprietary Information
Collect the trace information about the control (start, stop, etc.) requests from the cluster
software to Agent, and their results.
(11) Collect the information items (6), (7), and (8) on both the primary and secondary hosts. Note
that shared disk is mounted to the host when you execute the RAS command in the Active host
of Active-Standby cluster system.
If conversion of the CSV report format by using the htm-csv-convert command fails, the following
data must be obtained:
(13) The input file specified in htm-csv-convert
When the problems occurred in the jpctdraidperf command execution, the following data must be
obtained:
(14) The CSV file which jpctdraidperf command outputs
When the problems occurred in the htmrest command execution, the following data must be
obtained:
(15) Contents of standard output and standard error output obtained when specifying the --debug
option to execute the command.
The following is an example of the command executed when the --debug option is specified.
Example:
htmrest GET http://localhost:22015/DeviceManagerWebService/analytics/v1/objects/alert
-defs -u user -p password --debug > C:\tmp\htmrest_result.txt 2>&1
Table 4.1-1: List of products and applicable RAS information collection commands
Product hcmdsgetlogs htm-getlogs htm- jpcprras jpcras hinstgetlogs
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
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
Installer Y Y Y Y Y Y N N Y N
(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
not collect RAS information for Linux because Linux does not support Tuning Service.
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:
[ In Ver.8 or later ]
In Windows:
Suite-installation-directory\Base\bin\hcmds64getlogs /dir C:\Logs
In Linux:
# <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin/hcmds64getlogs
-dir /export/Logs
Notes:
- In Tuning Manager Ver.8.1.4 or later, if the hcmds64getlogs command shown above does not
exist, execute the hinstgetlogs command. For details about the hinstgetlogs command, see the
Hitachi Command Suite Software Troubleshooting Guide.
Note that hinstgetlogs is an open tool for the Support Center.
- The data acquired using the hcmdsgetlogs or the hcmds64getlogs command is saved in an
archive file with the extension .jar.
The .jar archive files can be unpacked using the jar command included in J2SDK.
Since J2SDK is included in the Hitachi Storage Command Suite Common Component, on a
Windows machine where Tuning Manager server is installed, you can unpack the .jar archive
files by executing the following command:
[ In Ver.6 to earlier than 8 ]
> "C:\Program Files\HiCommand\Base\jdk\bin\jar.exe" -xvf path-name
[ In Ver.8 or later ]
> "C:\Program Files\HiCommand\Base64\uCPSB\jdk\bin\jar.exe" -xvf path-name
In the above, path-name is the path name of the HiCommand_log.jar file.
The compression format of .jar files is the same as the ZIP format. Therefore, you may be able
to use unzip software to unpack .jar files by changing the extension from .jar to .zip. Note that,
in this case, the archive files may be unpacked incorrectly.
(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
(4.3) Terms
The following terms are used in this section.
Table 4.1.1-2: Terms used in this chapter
# Terms Directory
(x86)
%SystemDrive%\Program Files\HiCommand\Base
[ In Ver.8 or later ]
%SystemDrive%\Program Files\HiCommand\Base64
2 (x86)
%SystemDrive%\Program Files\HiCommand\TuningManager
%SystemDrive%\Program Files
(x86)\HiCommand\TuningManager
[ In Ver.8 or later ]
%SystemDrive%\Program Files\HiCommand\TuningManager
(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] +
* 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:
Procedure
* 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
[d] The size of RAS information for the Agent for RAID, installed on the same See (4.5.4)
[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)
# Solaris
1 /opt/HiCommand/Base
2 /var/opt/HiCommand/Base
3 /opt/HiCommand/TuningManager
4 /var/opt/HiCommand/TuningManager
5 /opt/jp1pc (*1)
Log output directory specified by the config.xml file for PerformanceReporter (If not specified,
6
/opt/HiCommand/TuningManager/PerformanceReporter/log)
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)
Log output directory specified by the config.xml file for PerformanceReporter (If not specified,
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
1 /var/adm/messagesX *1
1 /var/log/messages[.X]
(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]
85 Hitachi Proprietary Information
/opt/HiCommand/Base/bin/hcmdsdbpath
[For Linux]
- In Ver.6 to earlier than 8
<Hitachi-Command-Suite-Common-Component-Installation-directory>/bin/hcmdsdbpath
- In Ver.8 or later
<Hitachi-Command-Suite-Common-Component-Installation-directory>/sbin/hcmdsdbpath
Output example
HDVM_RD C:\Program
Files\HiCommand\DeviceManager\HiCommandServer\database\DeviceManager\RD_HDVM
(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
[ In Ver.8 or later ]
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
[ In Ver.8 or later ]
(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.1) Open the command prompt.
(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
Area Path:
C:\Program Files\HiCommand\TuningManager\database\TuningManager\TM00
[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
1 opt/jp1pc/mgr/store/backup
Procedure
[i] The total sum of the capacities indicated by the pdinfoget -m command See (4.6.1)
(4.6.1) Estimating [i]: the total sum of the capacities indicated by the pdinfoget - m command
(4.6.1.1) Open the command prompt.
(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
1 PDDIR /opt/HiCommand/Base/HDB
3 LD_LIBRARY_PATH /opt/HiCommand/Base/HDB/lib
4 PATH /opt/HiCommand/Base/HDB/bin
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
4 Shell other than the above refer to the manual of each shell.
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
# Command
Display result
PDDIR=/opt/HiCommand/Base/HDB
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
of
shell
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 LD_LIBRARY_PATH
export PATH
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}
other
than
the
above
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
# Command
Display result
PDDIR=<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB
1 pdinfoget -m
(4.6.1.4) [i] indicates the total sum of the values for the init_directory and
detail_directory.
init_directory = 41 Mbyte
[C] = (Total capacity of the databases that are used by Tuning Manager)
(4.7.1) Confirming the total capacity of the databases that are used by Tuning Manager
(4.7.1.1) Open the command prompt.
(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
[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.
- RAS information acquisition fails due to insufficient free disk space.
- 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
(2) Prerequisites
- To execute this command, you must have logged on as a member of the Administrators
group, root, or the equivalent.
- This command must be executed on a machine where Tuning Manager server is
installed.
- You do not need to stop the Tuning Manager server services.
- To acquire the database information about Tuning Manager Agent, the Agent services
must be stopped.
(3) Use
For details about how to use this command, see the manual.
For a list of log files acquired using this command, see Exhibit 1 Maintenance information.
Example:
In Windows:
Suite-installation-directory\TuningManager\bin\htm-getlogs -d C:\Logs -z
In Solaris:
# /opt/HiCommand/TuningManager/bin/htm-getlogs -d /export/Logs -z
In Linux:
# <TuningManager-Installation-directory> /bin/htm-getlogs -d /export/Logs -z
(2) Prerequisites
- To execute this command, you must have logged on as a member of the Administrators
group, root, or the equivalent.
- This command must be executed on a machine where Tuning Manager server is
installed.
- You do not need to stop the Tuning Manager server services.
(3) Use
For details about how to use this command, see the manual.
For a list of log files acquired using this command, see Exhibit 1 Maintenance information.
Example:
In Windows:
Suite-installation-directory\TuningManager\bin\htm-dump -d C:\Logs -z
In Solaris:
# /opt/HiCommand/TuningManager /bin/htm-dump -d /export/Logs -z
In Linux:
# <TuningManager-Installation-directory> /bin/htm-dump -d /export/Logs -z
Example:
In Windows:
Suite-installation-directory\TuningManager\PerformanceReporter\tools\jpcprras C:\Logs
In Solaris:
# /opt/HiCommand/TuningManager/PerformanceReporter/tools/jpcprras /export/Logs
In Linux:
# <TuningManager-Installation-directory>/PerformanceReporter/tools/jpcprras /export/Logs
Example 1: When acquiring the log and database information about Collection Manager and all
Agents running on the host where the jpcras command is executed
In Windows:
cd Suite-installation-directory\TuningManager\jp1pc\tools\
jpcras C:\Logs all all
In Unix (Linux, Solaris):
# cd /opt/jp1pc/tools
# jpcras /export/Logs all all
Example 2: When acquiring the log and database information about RAID Agent from Agent
running on the host where the jpcras command is executed
In Windows:
cd Suite-installation-directory\TuningManager\jp1pc\tools
jpcras C:\Logs agtd all
In Unix (Linux, Solaris, HP-UX, or AIX):
# cd /opt/jp1pc/tools
# jpcras /export/Logs agtd all
Example 3: When acquiring the log and database information about RAID Agent whose instance
name is LightningA from Agent running on the host where the jpcras command is executed
In Windows:
cd Suite-installation-directory\TuningManager\jp1pc\tools
jpcras C:\Logs agtd all inst=LightningA
In Unix (Linux, Solaris, HP-UX, or AIX):
# cd /opt/jp1pc/tools
# jpcras /export/Logs agtd all inst=LightningA
Note:
If the installation log for Collection Manager (pfm_inst.log) is not found in the folder specified by
the environment variable %TEMP%, an attempt to install the software or collect logs might be
performed on a remote desktop connection when a remote session is held. In this case, use the
GUI to select [System Properties], the [Advance] tab, and then [Environment Variables]. After you
select [Environment Variables], check the value of the environment variable %TEMP% to
determine whether the log output is directed to the folder specified by the variable %TEMP% or a
subfolder of that folder. The following is an example of an output destination:
If you install the software in a remote desktop connection environment for a remote session, the
installation log output is directed to an automatically generated folder. Because this folder is
deleted when you log off, if you want to collect the installation log data, you must collect it before
[For Agent]
Refer to the section, Collecting information if an installation failure occurs of the following
manual:
- In Ver.6
Hitachi Tuning Manager Software Installation Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Installation Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Installation Guide
If the jpcras command cannot be used, please get following log files manually.
Table 4.2.2-1:The list of log files manually collected when the jpcras command cannot be used
# Log File Name Log Location OS Installed PP
server,
Agents
(application), server,
Eventlog(system) Agents
/var/adm/syslog/syslog.log Agents
- Case Solaris
- In Windows:
<Tuning Manager server Installation
folder>\agtw\agent\instance-name\javacoreprocessID.YYMMDDhhmmss.txt
- 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.
(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.
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
<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
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:
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.
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
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
3
Figure 4.1-2 Command Prompt window
- In Solaris, Linux:
Start the console.
- In Solaris, Linux:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/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.
- In Solaris, Linux:
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.
(3) In the DCFM menu, click Monitor, Technical Support, and then Switch / Host SupportSave.
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.
- In Solaris, Linux:
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.
- In Solaris, Linux:
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)
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)
- In Windows:
- In Solaris, Linux:
11
5. Collecting Detailed XML Trace Log Data
This chapter describes how to collect detailed XML trace log data.
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcras
path-to-directory-where-maintenance-information-is-stored agtw all
- In Solaris, Linux:
/opt/jp1pc/tools/jpcras
path-to-directory-where-maintenance-information-is-stored agtw all
(For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.)
When you execute the command, the following message appears and maintenance
information is collected:
Verify that the following message is output. If it is output, collection has successfully
ended.
12
Figure 5.1-2 Display when maintenance information collection has successfully ended
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1
13
Detailed XML trace log output directory:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name
File to be deleted:
CIMClientXML_Trace[?].txt
- In Windows:
- In Solaris, Linux:
-End of document-
14
Collecting XML trace and SMI Agent for FOS logs when using
SMI Agent for FOS to monitor Brocade switches (B-Model)
1. Overview
If an error occurs in an HTnM - Agent for SAN Switch (hereafter Agent for SAN Switch) instance
that uses SMI Agent for FOS to monitor Brocade switches (B-Model), you must collect the SMI
Agent for FOS CIMOM log data, Provider log data, and all other data including communication
data.
XML trace log data is output when Agent for SAN Switch is used to monitor Brocade
Switches (B-Model).
The XML trace log data is output at the following two levels:
The default setting is Level 1. For this level, only timestamps are output.
If a failure occurs while Brocade Switches (B-Model) are being monitored, and the
failure seems to have been caused by an FC switch (for example, there are no
communication problems but the data is not correct), set the log output level to Level
2 to collect all data, including communication data (referred to hereafter as detailed
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
- SMI Agent for FOS 120.7.2 (Windows/Solaris/Linux)
- SMI Agent for FOS 120.8.0 (Windows/Solaris/Linux)
- SMI Agent for FOS 120.9.0 (Windows/Solaris/Linux)
- SMI Agent for FOS 120.11.0 (Windows/Solaris/Linux)
3. Notes
When you collect SMI Agent for FOS CIMOM log data, provider log data and detailed
XML trace log data, note the following:
(1) When you collect the CIMOM log data, provider log data and detailed XML trace log
data, you must specify the configuration beforehand according to the procedures
described in 4. Preconfiguration for Collecting CIMOM log Data and Provider log
Data.
(2) To collect the CIMOM log data, provider log data and detailed XML trace log data,
you must temporarily stop the Agent for SAN Switch instance.
(3) When you collect the CIMOM log data and provider log data, make sure that there is
enough space on the drive where SMI Agent for FOS is installed. SMI Agent for FOS
data requires a lot of disk space.
(4) When you collect detailed XML trace log data, make sure that there is enough disk
space on the drive on which HTM is installed, because the amount of detailed XML
trace log data is very large.
When you collect detailed XML trace log data, you specify a file size and the number
of files. However, the size for one line of detailed XML trace log data is large, so the
specified file size might be exceeded. Accordingly, the procedure described in this
document requires about 320 MB 1 of free disk space.
(5) Since the CPU usage rate increases when you collect CIMOM log data and provider
log data, SMI Agent for FOS performance might be significantly degraded.
Therefore, when the data on SMI Agent for FOS has been collected, restore the
original configuration by performing the procedure described in 6. Procedure for
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
data. Therefore, the file size might reach 5 MB x 64 (number of files) = 320 MB.
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
certain properties defined in the following file:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
3
4.1. Stopping the Agent for SAN Switch instance
(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
- In Solaris, Linux:
Start the console.
- In Solaris, Linux:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
When SMI Agent for FOS is used to monitor Brocade switches (B-Model), either of the
following messages may be displayed and a timeout may occur depending on the size
of the instance that is being monitored. If a timeout occurs, wait a while before
executing the above command to make sure that the instance has stopped (the status
is Inactive).
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)
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
- In Solaris, Linux:
Start Brocade SMI Agent Configuration Tool by executing the following command:
SMI-Agent-for-FOS-installation-directory/agent/server/jserver/bin/configurationtool.sh
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
data will be output.
(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)
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
(1) Displaying the window for configuring CIMOM log
In the Menu tree, under Debugging And Logging, choose CIMOM.
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)
11
4.4. Configuring Provider log
(1) Displaying the window for configuring Provider log
In the Menu tree, under Debugging And Logging, choose Provider.
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
data will be output.
(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)
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)
15
4.5. Specifying output settings for the detailed XML trace log data
(1) Open the jpcagt.ini file.
Use a text editor to open the jpcagt.ini file located in:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
16
(2) Change the values of properties related to the XML trace log.
In the Agent section, change the values of the properties related to the XML trace log
as follows:
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2
17
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.
- In Solaris, Linux:
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.
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.
SMI-Agent-for-FOS-installation-directory\agent\server\jserver\bin
- In Solaris, Linux:
SMI-Agent-for-FOS-installation-directory/agent/server/jserver/bin
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
file-name-specified-as-log-file[?]
20
5.6. 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
- In Solaris, Linux:
/opt/jp1pc/tools/jpcras
path-to-directory-where-maintenance-information-is-stored agtw all
For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.
When you execute the command, the following message appears and maintenance
information is collected:
21
If the following message appears, collection was successful.
22
6. Procedure for Restoring the Environment
When data collection by SMI Agent for FOS is complete, perform the following
procedure to restore the original configuration.
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)
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
(1) Displaying the window for configuring CIMOM log
In the Menu tree, under Debugging And Logging, choose CIMOM.
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)
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.
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)
28
6.3. Restoring settings
(1) Open the jpcagt.ini file.
Use a text editor to open the jpcagt.ini file located in:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name
CIMClientXML_Trace[?].txt
29
6.5. Restarting SMI Agent for FOS
Click the Start Server button to restart SMI Agent for FOS.
-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
- Product Status Log
- Threshold Alert Log
(B)If DCFM is used for monitoring, log in to DCFM Server from DCFM Client, and then
acquire the following logs:
- Audit Log
- Event Log
- Fabric Log
- FICON Log
- Product Status Log
- Security Log
- Syslog Log
- Technical Support Information
(C) Please collect detailed XML trace log and SMI Agent for EOS log data by the
following procedure.
How_to_collect_deta
iled_XML_TraceLog(E
(B) please collect detailed XML trace log data by the following procedure.
How_to_collect_deta
iled_XML_TraceLog(S
1. Overview
If an error occurs in a HTnM - Agent for SAN Switch (hereafter Agent for SAN Switch)
instance that uses SMI Agent for EOS to monitor Brocade switches (M-Model), you must collect
the SMI Agent for EOS audit log data and the debug log data.
In addition to the SMI Agent for EOS audit log data and debug log data, you must
also collect XML trace log data that contains all output data including data about
communication between Agent for SAN Switch and SMI Agent for EOS.
The XML trace log data is output at the following two levels:
The default setting is Level 1. For this level, only timestamps are output.
If a problem occurs, set the log output level to Level 2 to collect all data, including
communication data (referred to hereafter as detailed XML trace log data).
This document describes how to collect audit log data and debug log data as well as
detailed XML trace log data.
2. Prerequisites
(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
trace log data is very large.
When you collect detailed XML trace log data, you specify a file size and the number
of files. However, one line of detailed XML trace log data also contains such a large
amount of data that the file with the specified file size might overflow. Accordingly,
the procedure described here requires about 320 MB 1 of free disk space.
(6) Since the CPU usage rate increases when you collect debug log data, the SMI Agent
for EOS performance might be significantly degraded.
Therefore, when debug log data has been collected, restore the original configuration
by performing the procedure described in 6. Procedure for Restoring the Environment.
(7) Since the CPU usage rate increases when you collect detailed XML trace log data,
the Agent for SAN Switch performance might be significantly degraded.
Therefore, when detailed XML trace log data has been collected, restore the original
configuration by performing the procedure described in 6. Procedure for Restoring the
Environment.
4. Preconfiguration Required for Collecting Debug Log Data and Detailed XML
Trace Log Data
To collect debug log data, you must change the configuration by using Server
Configuration Tool provided by SMI Agent for EOS.
To output detailed XML trace log data, you must manually change the values set for
certain properties defined in the following file:
1Given 4096 KB (file size) x 64 (number of files) = 256 MB, the actual file size might be as
much as 1 MB larger than the specified size, depending on the output format of the XML
data. Therefore, the file size might reach 5 MB x 64 (number of files) = 320 MB.
2
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
3
Figure 4.1-2 Command Prompt window
- In Solaris, Linux:
Start the console.
- In Solaris, Linux:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
4
4.2. Starting Server Configuration Tool
(1) 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).
- In Solaris, Linux:
Start Server Configuration Tool by executing the following command from the
console:
SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin/McDATA_server_c
onfiguration_tool.sh
5
Figure 4.2-2 Server Configuration Tool login window
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)
4.5. Specifying output settings for detailed XML trace log data
(1) Opening the jpcagt.ini file
- In Windows:
Open the Suite-installation-directory\TuningManager
\jp1pc\agtw\agent\instance-name\jpcagt.ini file using a text editor.
7
- In Solaris, Linux:
Open the /opt/jp1pc/agtw/agent/instance-name/jpcagt.ini file using an editor.
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2
8
Figure 4.5-2 jpcagt.ini file (for Windows, after setting changes)
- In Solaris, Linux:
Stop SMI Agent for EOS by executing the following command:
SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin/stop_server.sh
9
SMI_Agent_for_EOS_products_2.7, and then Start Service to start SMI Agent for
EOS.
- In Solaris, Linux:
Start SMI Agent for EOS by executing the following command:
SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin/start_server.sh
- In Windows:
- In Solaris, Linux:
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.
10
5.3. Executing the tool for collecting SMI Agent for EOS log data
Using the tool for collecting SMI Agent for EOS log data, obtain the necessary log
data. Execute the following command:
- In Windows:
cd /d SMI-Agent-for-EOS-installation-directory\agent\server\jserver\bin
statusexporter.bat
- In Solaris, Linux:
cd SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin
statusexporter.sh
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
- In Solaris, Linux:
Log data collection tool output folder name:
SMI-Agent-for-EOS-installation-directory/agent/server/jserver/bin
11
5.4. 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
- In Solaris, Linux:
/opt/jp1pc/tools/jpcras
path-to-directory-where-maintenance-information-is-stored agtw all
(For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.)
When you execute the command, the following message appears and maintenance
information is collected:
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
13
Figure 6.1-1 Window for debug log configuration (before configuration restoration)
14
Figure 6.1-2 Window for debug log configuration (after configuration restoration)
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
15
Change the [Agent] section as follows:
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name
File to be deleted:
CIMClientXML_Trace[?].txt
16
- In Windows:
- In Solaris, Linux:
-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.
The XML trace log data is output at the following two levels:
The default setting is Level 1. For this level, only timestamps are output.
If a failure occurs while Cisco switches are being monitored, and the failure seems to
have been caused by an FC switch (for example, there are no communication problems
but the data is not correct), set the log output level to Level 2 to collect all data,
including communication data (referred to hereafter as detailed XML trace log data).
This document describes how to collect detailed XML trace log data.
2. Prerequisite Product
- HTnM - Agent for SAN Switch for Windows Version 5.9.0-00 or later
- HTnM - Agent for SAN Switch for Solaris Version 6.1.0-00 to earlier than 8.0.0
- HTnM - Agent for SAN Switch for Linux Version 7.1.0-00 or later
3. Notes
This section provides notes on collecting detailed XML trace log data.
(1) Before you can collect detailed XML trace log data, you must change the settings as
described in 4. Procedure for collecting detailed XML trace log data.
(2) To collect detailed XML trace log data, you must first stop all Agent for SAN Switch
instances.
(3) When you collect detailed XML trace log data, make sure that there is enough disk
space on the drive on which HTnM is installed, because the amount of detailed XML
trace log data is very large.
1
When you collect detailed XML trace log data, you specify a file size and the number
of files. However, the size for one line of detailed XML trace log data is large, so the
specified file size might be exceeded. Accordingly, the procedure described in this
document requires about 320 MB 1 of free disk space.
(4) While detailed XML trace log data is being collected, the CPU usage rate becomes
high. As a result, the performance of Agent for SAN Switch could significantly
degrade.
Therefore, after detailed XML trace log data is collected, restore the original settings
as described in 6. Restoring the environment.
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
1 Although 4096 KB (file size) x 64 (number of files) = 256 MB, the actual file size might be
as much as 1 MB larger than the specified size, depending on the output format of the XML
data. Therefore, the file size might reach 5 MB x 64 (number of files) = 320 MB.
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.)
3
- In Solaris, Linux:
Start the console.
- In Solaris, Linux:
Even if the above command terminated normally, execute the following command to
confirm that the instance stopped (the status is "Inactive"):
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
4
4.2. Specifying output settings for the detailed XML trace log data
(1) Open the jpcagt.ini file.
Use a text editor to open the jpcagt.ini file located in:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
5
(2) Change the values of properties related to the XML trace log.
In the Agent section, change the values of the properties related to the XML trace log
as follows:
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2
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:
- In Solaris, Linux:
When the data collection event starts after the instance has started, detailed XML
trace log data is output to the directory shown below. If a failure occurs, stop the
instance as described in 4.1. Stopping an instance of Agent for SAN Switch.
Output directory:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name
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.
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstop agtw
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstop agtw
Even if the above command terminated normally, execute the following command to
confirm that the instances stopped (the status is "Inactive"):
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
9
5.2. Collecting information by executing 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
- In Solaris, Linux:
/opt/jp1pc/tools/jpcras
path-to-directory-where-maintenance-information-is-stored agtw all
For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.
When you execute the command, the following message appears and maintenance
information is collected:
10
If the following message appears, collection was successful.
11
6. Restoring the environment
After the collection of detailed XML trace log data finishes, perform the following
procedure to restore the original settings.
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1
12
6.3. Deleting XML trace log data
This section describes how to delete detailed XML trace log data.
Delete the following files:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name
CIMClientXML_Trace[?].txt
-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
- 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
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.
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
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.
The XML trace log data is output at the following two levels:
The default setting is Level 1. For this level, only timestamps are output.
If a failure occurs while Cisco switches are being monitored, and the failure seems to
have been caused by an FC switch (for example, there are no communication problems
but the data is not correct), set the log output level to Level 2 to collect all data,
including communication data (referred to hereafter as detailed XML trace log data).
This document describes how to collect detailed XML trace log data.
2. Prerequisite Product
- HTnM - Agent for SAN Switch for Windows Version 7.2.1-00 or later
- HTnM - Agent for SAN Switch for Solaris Version 7.2.1-00 to earlier than 8.0.0
- HTnM - Agent for SAN Switch for Linux Version 7.2.1-00 or later
3. Notes
This section provides notes on collecting detailed XML trace log data.
(1) Before you can collect detailed XML trace log data, you must change the settings as
described in 4. Procedure for collecting detailed XML trace log data.
(2) To collect detailed XML trace log data, you must first stop all Agent for SAN Switch
instances.
(3) When you collect detailed XML trace log data, make sure that there is enough disk
space on the drive on which HTnM is installed, because the amount of detailed XML
trace log data is very large.
1
When you collect detailed XML trace log data, you specify a file size and the number
of files. However, the size for one line of detailed XML trace log data is large, so the
specified file size might be exceeded. Accordingly, the procedure described in this
document requires about 320 MB 1 of free disk space.
(4) While detailed XML trace log data is being collected, the CPU usage rate becomes
high. As a result, the performance of Agent for SAN Switch could significantly
degrade.
Therefore, after detailed XML trace log data is collected, restore the original settings
as described in 6. Restoring the environment.
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
1 Although 4096 KB (file size) x 64 (number of files) = 256 MB, the actual file size might be
as much as 1 MB larger than the specified size, depending on the output format of the XML
data. Therefore, the file size might reach 5 MB x 64 (number of files) = 320 MB.
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.)
3
- In Solaris, Linux:
Start the console.
- In Solaris, Linux:
Even if the above command terminated normally, execute the following command to
confirm that the instance stopped (the status is "Inactive"):
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
4
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.
(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
4.3. Specifying output settings for the detailed XML trace log data
(1) Open the jpcagt.ini file.
Use a text editor to open the jpcagt.ini file located in:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
7
(2) Change the values of properties related to the XML trace log.
In the Agent section, change the values of the properties related to the XML trace log
as follows:
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=64
XML_TRCLOG_LEVEL=2
8
4.4. 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:
- In Solaris, Linux:
When the data collection event starts after the instance has started, detailed XML
trace log data is output to the directory shown below. If a failure occurs, stop the
instance as described in 4.1. Stopping an instance of Agent for SAN Switch.
Output directory:
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name
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.
Suite-installation-directory\TuningManager\jp1pc\tools\jpcstop agtw
- In Solaris, Linux:
/opt/jp1pc/tools/jpcstop agtw
Even if the above command terminated normally, execute the following command to
confirm that the instances stopped (the status is "Inactive"):
- In Windows:
Suite-installation-directory\TuningManager\jp1pc\tools\jpcctrl list *
- In Solaris, Linux:
/opt/jp1pc/tools/jpcctrl list *
11
5.2. Collecting information by executing 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
- In Solaris, Linux:
/opt/jp1pc/tools/jpcras
path-to-directory-where-maintenance-information-is-stored agtw all
For details about the jpcras command, refer to the HTnM-Tuning Manager
documentation.
When you execute the command, the following message appears and maintenance
information is collected:
12
If the following message appears, collection was successful.
13
6. Restoring the environment
After the collection of detailed XML trace log data finishes, perform the following
procedure to restore the original settings.
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name\jpcagt.ini
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name/jpcagt.ini
XML_TRCLOG_SIZE=4096
XML_TRCLOG_PAGE=8
XML_TRCLOG_LEVEL=1
14
6.3. Deleting XML trace log data
This section describes how to delete detailed XML trace log data.
Delete the following files:
Suite-installation-directory\TuningManager\jp1pc\agtw\agent\instance-name
- In Solaris, Linux:
/opt/jp1pc/agtw/agent/instance-name
CIMClientXML_Trace[?].txt
-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.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.
[ In Ver.8 or later ]
In Windows:
<Common-Component-installation-folder>\bin\hcmds64srv /stop /server TuningManager
In Linux:
<Common-Component-Installation-directory>/bin/hcmds64srv -stop -server TuningManager
Note:
A line starting with a hash mark (#) is handled as a comment line.
[ In Ver.8 or later ]
In Windows:
<Common-Component-installation-folder>\bin\hcmds64srv /start /server TuningManager
In Linux:
<Common-Component-Installation-directory>/bin/hcmds64srv -start -server TuningManager
4.4.2 Number, size, and output level of Hybrid Store trace log files
To change the number, size, and output level of Hybrid Store trace log files
(htmRestDbEngineTrace.log), add properties and values to the
sdblogger.properties private properties file.
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.
2) Open the sdblogger.properties file in a text editor, add properties in the format
below, and then save the file. For details about the values to be specified, see Table 4.4-2.
<key>=<value>
Note:
A line starting with a hash mark (#) is handled as a comment line.
3) Restart the service of the Tuning Manager Agent REST API component.
In Windows:
<Agent-Installation-folder>\htnm\bin\htmsrv start -webservice
In Linux:
<Agent-Installation-directory>/htnm/bin/htmsrv start -webservice
4.5 The problems in acquiring RAS information and the contingency plan. (Only in
Ver.6.4)
The problems and their solutions described in this section only apply to version 6.4. They do not
apply to version 7.0 or later, or to version 6.3 or earlier.
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
- 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.
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
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.
(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):
# cd /opt/jp1pc/tools
# ./jpcras /export/Logs all all
- STEP2
If Software division require the result of the STEP2, send the result to Software division.
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:
For Solaris:
/opt/HiCommand/Base/bin/hcmdssrv -stop -server TuningManager
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmdssrv stop
-server TuningManager
[ In Ver.8.0.0 or later ]
For Windows:
<Hitachi-Command-Suite-CommonComponent-installation-folder>\bin\hcmds64srv /stop
/server TuningManager
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmds64srv stop
-server TuningManager
For Solaris:
/opt/HiCommand/TuningManager/conf/user.properties
Use a text editor to open the user property file and add the dumpChartXML property as follows:
dumpChartXML=true
For Solaris:
/opt/HiCommand/Base/bin/hcmdssrv -start -server TuningManager
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmdssrv start
-server TuningManager
[ In Ver.8.0.0 or later ]
For Windows:
<Hitachi-Command-Suite-Common-Component-installation-folder>\bin\hcmds64srv /start
/server TuningManager
For Linux:
<Hitachi-Command-Suite-Common-Component-installation-directory>/bin/hcmds64srv start
-server TuningManager
(4) Log in to the Main Console and display the chart in which the problem occurred.
Log in to Main Console and display the chart that failed to display correctly. The dump file that
contains the chart information is output when you display the chart.
For Solaris:
/opt/HiCommand/TuningManager/logs
For Linux:
<Tuning-Manager-server-installation-directory>/logs
(9) Delete the dump file that contains the chart information.
Delete the dump file you checked in step (5).
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)
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)
1 Hitachi Storage Command This service provides common function of Hitachi Storage
Suite Common Web Service Command Suite, such as consolidated Log in (SSO),
2 Hitachi Storage Command This service provides the consolidated Log in function (SSO)
3 Hitachi Storage Command This service provides the interface for getting data from Agent
7.1 or later.
4 Hitachi Storage Command This service is the main service of Tuning Manager server.
5 Inter Base/Inter Client Inter Base is used by HTnM and HDvM in version 3.5 or
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
Collection Manager/Agents.
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.
15 Agent Store This service manages Agents DB, stores the data got by Agent
Collector.
[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.
1. Tuning Manager REST Service This service receives requests from Tuning Manager API, and
2. Agent REST Service This service receives requests from Tuning Manager REST
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
Collection Manager/Agents.
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
15. Agent Store This service manages Agents DB, stores the data got by Agent
Collector.
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)
# Service Name of process Explanation
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
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)
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
Collection Manager/Agents.
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
15 Agent Store This service manages Agents DB, and stores and returns the
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
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
Collection Manager/Agents.
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
15. TCP/IP Collector This process exists only when Agent for RAID uses TCP/IP
16. Reciever This process exists only when Agent for RAID uses TCP/IP
Collector.
17. Agent Store This service manages Agents DB, and stores and returns the
Register the
service id
information
Register the
event information
Agent Store
Correlator
[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.
End
No Has the
core been
initialized?
Yes
Figure 5.2.2-1 Overview of the startup sequence for the Tuning Manager server
[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.
End
Service:
[ In Ver.6 to earlier than 8 ]
- HiRDB/EmbeddedEdition _HD0
[ In Ver.8 or later ]
- HiRDB/EmbeddedEdition _HD1
This service is not used for starting or stopping HiRDB services. It is used for
controlling HiRDB services and needs to run continuously.
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)
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
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
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.
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
a) Execute the following command (*2) to stop Tuning Manager server on the host where the Tuning
Manager server is installed (*3).
[For Windows]
<Common-Component-installation-folder>\bin\hcmdssrv /stop /server TuningManager
[For Solaris]
/opt/HiCommand/TuningManager/bin/hcmdssrv -stop -server TuningManager
b) Execute the following command (*2) to stop agents connected the Tuning Manager server on
each host where the agent is installed (*4).
[For Windows]
<Agent-installation-folder>\tools\jpcstop <servicekey> [inst=<instance name>]
[For UNIX]
/opt/jp1pc/tools/jpcstop <servicekey> [inst=<instance name>]
c) Execute the following command (*2) to start Tuning Manager server on the host where the
Tuning Manager server is installed.
[For Windows]
<Common-Component-installation-folder>\bin\hcmdssrv /start /server TuningManager
[For Solaris]
/opt/HiCommand/TuningManager/bin/hcmdssrv -start -server TuningManager
d) Execute the following command (*2) to start Tuning Service on the host where the Tuning
Manager server is installed.
[For Windows]
<Common-Component-installation-folder>\bin\hcmdssrv /start /server TuningService
[For Solaris]
/opt/HiCommand/TuningManager/bin/hcmdssrv -start -server TuningService
e) Execute the following command (*2) to start agents connected the Tuning Manager server on
each host where the agent is installed.
[For Windows]
<Agent-installation-folder>\tools\jpcstart <servicekey> [inst=<instance name>]
[For UNIX]
/opt/jp1pc/tools/jpcstart <servicekey> [inst=<instance name>]
The issue will not be resolved after this recovery or the message KAVY20024-E is not found in the
Tuning Service logs, see the following manual and execute the operation against KATS63030-E.
- In Ver.6
Hitachi Tiered Storage Manager Software Messages
135 Hitachi Proprietary Information
- In Ver.7
Hitachi Command Suite Software Messages Guide
If the shared disk resource is failed over while the HiRDB service is running following a failure of
the hcmdsdbclustersetup command, HiRDB cannot start.
In this case, the recovery must be performed as follows by editing the HiRDB definition file, which
has not been released as a product.
Recovery procedure
Perform the following procedure only on the executing node in a cluster configuration.
(2) Make sure that the shared disk to which the database for Hitachi Storage Command Suite
products is to be migrated has enough free space to hold the database. If there is not enough free
space, secure more free space.
(6) Use the following command to confirm that the HiRDB service has started.
[ In Ver.6 to earlier than 8 ]
hcmdsdbsrv /status
[ In Ver.8 or later ]
hcmds64dbsrv /status
If the following message is output, the HiRDB service has started:
KAPM06440-I The HiRDB service has already started. is output.
(7) Re-execute the following command by specifying the options that were used when the previous
execution failed.
[ In Ver.6 to earlier than 8 ]
hcmdsdbclustersetup /createcluster /databasepath I:\share\HiCommand\HiRDB /exportpath
D:\HiCommand\work /auto
[ In Ver.8 or later ]
hcmds64dbclustersetup /createcluster /databasepath I:\share\HiCommand\HiRDB /exportpath
D:\HiCommand\work /auto
7.5. Caution for the case that HTnM is connected to HDvM 6.0.0 to 6.1.1 and is monitoring an
SMS series subsystem
The prerequisite version of HDvM for monitoring SMS series is 6.2.0 or later. If the following
conditions are met, SMS subsystem cannot be monitored by HTnM. Therefore the recovery
procedure described below should be executed.
Conditions
Recovery procedure
< Unless you are executing polling in connecting Agent for Server system that monitors a host
that SMS series connected to, skip the steps (6) and (7) below and continue executing the
procedure from the step (8). >
(6) Delete the service information of the Agent for Server System that monitors host connected to
SMS. For how to delete a service information, refer to the Hitachi Tuning Manager software
Agent Administration Guide.
(7) Perform a manual polling an hour or more after the last polling.
(8) Add an Agent for RAID and an Agent for Server System. About the way to add the agents, refer
to the Hitachi Tuning Manager software Server Administration Guide.
(9) Confirm gathered PD records. With Performance Reporter, you can confirm that reconnected
Agent for Server system and Agent for RAID have gathered PD records correctly.
(10) Perform a manual polling an hour or more after the last polling.
7.6. Using the jpcctrl delete command with the force option (this option is in
non-public to user), to forcibly delete node information
To remove an Agent from the group of Agents monitored by Tuning Manager Server, you must use
the jpcctrl delete command to delete the service information for the Agent managed by Collection
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".
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.
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
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.
<Components affected>
Software
HTnM server
HTnM - Agent for RAID
<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
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)>
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 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
#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.
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.
#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
Table 7.7-3: Location of the Store database error detection tool (HTnM 7.0)
# Ty OS Folder
pe
1 Windows 2003 none(*)
Server
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.
(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.
(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.
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.
By viewing these results, you can see that data in the Store database has been
corrupted.
The third and seventh lines show that the most recent data corruption occurred
on 2008/12/18.
(2) Solaris 10
,<In Ver.6.4>
*)Note that the execution procedure in a Solaris environment that is described in
this section assumes that the CD-ROM drive is mounted to the /cdrom/cdrom0
directory.
# Command line
1 /usr/sbin/mount -F cdfs -r device-special-file-name /cdrom/cdrom0
(a) Log in
Log in to the host as the root user. Alternatively, use the su command to switch to
152 Hitachi Proprietary Information
the root user.
The third and seventh lines show that the most recent data corruption occurred
on 2008/12/18.
The third and seventh lines show that the most recent data corruption occurred
on 2008/12/18.
Note: When this procedure is used, the version of HTnM Agents that was
used before the upgrade installation must be used.
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.
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.
Process completed.
Standard output
Error detection process was completed.
(S) Processing is ended.
[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.
(S) Continues processing.
(O) See 7.7.3.1 to take appropriate action.
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.
(S) Stops processing.
(a) Return codes that are output with the following message:
[Error] Backup processing failed. (rc = return-code)
(b) Return codes that are output with the following message:
[Error] Store version check processing failed. (rc= return-code)
(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)
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.
[ In Ver.6 to earlier than 8 ]
cd /d Suite-installation-directory\Base\HDB\BIN
[ In Ver.8 or later ]
cd /d Suite-installation-directory\Base64\HDB\BIN
2. Execute the following command. (This command sets the environment variable that is necessary
for executing command of HiRDB.)
pdntcmd
After executing "pdntcmd" command, operate the following procedures a) d), then confirm that the
environment variable is set correctly.
a) Execute "set PATH" command to confirm that the following two paths are added to the result.
[ In Ver.6 to earlier than 8 ]
Suite-installation-directory\Base\HDB\BIN
Suite-installation-directory\Base\HDB\CLIENT\UTL
[ In Ver.8 or later ]
Suite-installation-directory\Base64\HDB\BIN
Suite-installation-directory\Base64\HDB\CLIENT\UTL
b) Execute "set PDDIR" command and confirm that the result is following.
[ In Ver.6 to earlier than 8 ]
Suite-installation-directory\Base\HDB
[ In Ver.8 or later ]
Suite-installation-directory\Base64\HDB
< When the above character string is not defined in PDDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDDIR" command and confirm that the variable was defined correctly.
[ In Ver.6 to earlier than 8 ]
set PDDIR=Suite-installation-directory\Base\HDB
[ In Ver.8 or later ]
set PDDIR=Suite-installation-directory\Base64\HDB
c) Execute "set PDCONFPATH" command and confirm that the result is following.
[ In Ver.6 to earlier than 8 ]
Suite-installation-directory\Base\HDB\CONF
[ In Ver.8 or later ]
Suite-installation-directory\Base64\HDB\CONF
< When the above character string is not defined in PDCONFPATH variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDCONFPATH " command and confirm that the variable was defined correctly.
[ In Ver.6 to earlier than 8 ]
set PDCONFPATH=Suite-installation-directory\Base\HDB\CONF
[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.
[ In Ver.6 to earlier than 8 ]
< When the above character string is not defined in PDUXPLDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDUXPLDIR" command and confirm that the variable was defined correctly.
[ In Ver.6 to earlier than 8 ]
set PDUXPLDIR=Suite-installation-directory\Base\HDB\UXPLDIR
[ In Ver.8 or later ]
set PDUXPLDIR=Suite-installation-directory\Base64\HDB\UXPLDIR
e) Execute the following command to confirm whether other programs are connected to HiRDB:
pdls -d prc -a
Any programs that are connected to HiRDB are displayed in the PROGRAM column of the
command execution results. Refer to the table Character strings displayed in the PROGRAM
column after the pdls command is executed below for the meanings of the character strings
displayed in the PROGRAM column.
An execution example is shown in Example of pdls -d prc -a command execution results below in
Example of the pdls -d prc -a command execution results.
Character strings displayed in the PROGRAM column after the pdls command is executed
Character string Connected program
Ver.6 htm 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.
C-GRP
...
C-GRP
...
C-GRP
...
[In Solaris]
1. Change current directory to "bin" directory of the install directory of Common Component
database.
cd /opt/HiCommand/Base/HDB/bin
2. Execute the following command. (This command sets the environment variable that is necessary
for executing command of HiRDB.)
. ./pduxenv
Note: A space is needed between "." and "./pduxenv".
After executing "pduxenv" command, operate the following procedures a) d), then confirm that the
environment variable is set correctly.
a) Execute "echo $PATH" command to confirm that the following path is added to the result.
/opt/HiCommand/Base/HDB/bin
b) Execute "echo $PDDIR" command and confirm that the result is following.
/opt/HiCommand/Base/HDB
< When the above character string is not defined in PDDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $PDDIR" command and confirm that the variable was defined correctly.
PDDIR=/opt/HiCommand/Base/HDB;export PDDIR
c) Execute "echo $PDCONFPATH" command and confirm that the result is following.
/opt/HiCommand/Base/HDB/conf
< When the above character string is not defined in PDCONFPATH variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $PDCONFPATH" command and confirm that the variable was defined correctly.
PDCONFPATH=/opt/HiCommand/Base/HDB/conf;export PDCONFPATH
d) Execute "echo $LD_LIBRARY_PATH" command and confirm that the result is following.
173 Hitachi Proprietary Information
/opt/HiCommand/Base/HDB/lib
< When the above character string is not defined in PDUXPLDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $LD_LIBRARY_PATH" command and confirm that the variable was defined
correctly.
LD_LIBRARY_PATH=/opt/HiCommand/Base/HDB/lib;export LD_LIBRARY_PATH
e) Execute the following command to confirm whether other programs are connected to HiRDB:
pdls -d prc -a
Any programs that are connected to HiRDB are displayed in the PROGRAM column of the
command execution results. Refer to the table Character strings displayed in the PROGRAM
column after the pdls command is executed below for the meanings of the character strings
displayed in the PROGRAM column.
An execution example is shown in Example of pdls -d prc -a command execution results below in
Example of the pdls -d prc -a command execution results.
Character strings displayed in the PROGRAM column after the pdls command is executed
Character string Connected program
Ver.6 htm 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.
C-GRP
...
C-GRP
...
[In Linux]
1. Change current directory to "bin" directory of the install directory of Common Component
database.
cd <Hitachi Command Suite Common Component installation directory>/HDB/bin
2. Execute the following command. (This command sets the environment variable that is necessary
for executing command of HiRDB.)
. ./pduxenv
Note: A space is needed between "." and "./pduxenv".
After executing "pduxenv" command, operate the following procedures a) d), then confirm that the
environment variable is set correctly.
a) Execute "echo $PATH" command to confirm that the following path is added to the result.
<Hitachi Command Suite Common Component installation directory>/HDB/bin
b) Execute "echo $PDDIR" command and confirm that the result is following.
/opt/HiCommand/Base/HDB
< When the above character string is not defined in PDDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $PDDIR" command and confirm that the variable was defined correctly.
PDDIR=/opt/HiCommand/Base/HDB;export PDDIR
< When the above character string is not defined in PDCONFPATH variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $PDCONFPATH" command and confirm that the variable was defined correctly.
PDCONFPATH=<Hitachi Command Suite Common Component installation directory>/HDB/conf;export
PDCONFPATH
d) Execute "echo $LD_LIBRARY_PATH" command and confirm that the result is following.
/opt/HiCommand/Base/HDB/lib
< When the above character string is not defined in PDUXPLDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "echo $LD_LIBRARY_PATH" command and confirm that the variable was defined
correctly.
LD_LIBRARY_PATH=<Hitachi Command Suite Common Component installation
directory>/HDB/lib;export LD_LIBRARY_PATH
e) Execute the following command to confirm whether other programs are connected to HiRDB:
pdls -d prc -a
Any programs that are connected to HiRDB are displayed in the PROGRAM column of the
command execution results. Refer to the table Character strings displayed in the PROGRAM
column after the pdls command is executed below for the meanings of the character strings
displayed in the PROGRAM column.
An execution example is shown in Example of pdls -d prc -a command execution results below in
Example of the pdls -d prc -a command execution results.
Character strings displayed in the PROGRAM column after the pdls command is executed
Character string Connected program
Ver.7 or later htm@<IP address> HTNM server which is connected to the HDvM database
Note: 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.)
C-GRP
...
...
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.
"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>)
25 L(RUN) 4348 0 0 sds01 190205 htm 0(<HTnM server IP address>)
< Ver.7>
/opt/HiCommand/Base/HDB/bin/pdprcsls
Main Console HiRDB connections
HOSTNAME : <HDvM host name>(###)
NO STATUS PID UID GID SVID TIME PROGRAM C-PID C-GRP
39 L(RUN) 17270 0 1 sds01 181500 htm@<HTnM server IP address> 0(<HTnM server IP address>)
40 L(RUN) 17271 0 1 sds01 181501 htm@<HTnM server IP address> 0(<HTnM server IP address>)
Note: In Ver.7, All IP addresses might not be displayed for IPv6. In that case, execute Procedure 2.
/opt/HiCommand/Base64/HDB/bin/pdprcsls
Main Console HiRDB connections
HOSTNAME : <HDvM host name>(###)
NO STATUS PID UID GID SVID TIME PROGRAM C-PID C-GRP
39 L(RUN) 17270 0 1 sds01 181500 htm@<HTnM server IP address> 0(<HTnM server IP address>)
40 L(RUN) 17271 0 1 sds01 181501 htm@<HTnM server IP address> 0(<HTnM server IP address>)
Note: In Ver.7 or later, All IP addresses might not be displayed for IPv6. In that case, execute Procedure 2.
Procedure 2 (In case you use V6, or in case you use IPv6 in V7.0):
Use the following file to acquire the IP address of the HTnM server host that is
connecting to the destination HDvM host. The IP address can be identified by
checking the port numbers used by the HTnM server connecting to HDvM.
For details on the port numbers used by the HTnM server when connecting to
HDvM, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
IP address of the HTnM server host Port numbers used by the HTnM server when connecting to HDvM
- In Windows:
- In Solaris,Linux:
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
- In Windows:
- In Solaris,Linux:
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.
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.
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.
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.
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.
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.
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.
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
<InstanceName>/log/
<InstanceName>/log
6. htmRestMessagen.log <HTnM Install Directory>/logs Message logs or trace logs that are output by
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
(*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
If you encounter a symptom such as one of those shown above while you are using the Analytics tab,
first, review the relevant settings. The following subsections provide more detailed information
about the points to be reviewed.
7.12.3.1.2 Communication settings on the servers (HDvM server, HTnM server, and HTnM
Agent)
A) Name resolution must be performed correctly on all of these servers.
Point to be reviewed:
Make sure that the host names of all servers, including the local server, are correctly
specified in the hosts file (or the jpchosts file) on every server. If a DNS server is used to
perform name resolution, make sure that information about every server is correctly
registered on the DNS server.
Action (example):
Correctly specify the host name and IP address of each server in the hosts file (or the
jpchosts file) on every server. Alternatively, register the correct host information on the
193 Hitachi Proprietary Information
DNS server.
Note: Particularly in an environment in which an HTnM server or HTnM Agent computer
has multiple NICs, use the jpchosts file to specify the IP addresses that HTnM server and
HTnM Agent can use to communicate with each other. (For details, see 3.3.7 Example 6:
Unable to see any storage from Main Console due to a mistake in the network configuration
in the Hitachi Tuning Manager Log Information Analysis Guide.)
B) For servers that have a firewall enabled, the ports used by the HDvM and HTnM services
must be included in the firewall exceptions list.
Point to be reviewed:
Make sure that the port numbers used by the services are included in the firewall exceptions
list. For the ports used by the services, see the manuals of the respective products. (For
example, for the ports used by the HTnM service, see Ports used by a Tuning Manager
server in the Tuning Manager Software Server Administration Guide.)
Action (example):
Include the ports used by the HDvM and HTnM services in the firewall exceptions list.
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
B) When you set a value for the ownHost or ownPort properties, make sure that you
completely remove the commented-out line from the properties file. (See case study
SD4884688.)
<!-- The IPv4 address or host name that can connect to the Tuning Manager management server is specified.
To change it, use the value specified in configforclient.xml file.
--> This line must be removed.
<!--
<param name="ownHost" value=host1"/>
-->
This line must be removed.
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"
Point to be reviewed:
Review the record-data collection interval.
If you encounter a problem such as the one above, check whether the Symptoms and Conditions
of occurrence described below apply in the user environment.
Note:
Although HTnM provides a function for disabling the Tuning Manager API, it is assumed that
most users will want to keep the Tuning Manager API enabled. Therefore, only this document
describes how to identify and correct the problem.
Symptoms
1) On the Overview page of the Identify Performance Problems wizard, an attempt to
obtain storage information from HTnM fails, and error messages KAIC15633-E and
KAIC08850-E are displayed.
messages:
Unable to collect Tuning Manager data. (resource name = resourcename, metric name(s)
= metricname(s), cause = KAIC08850-E Information cannot be collected from Tuning
Manager. A connection to the agent from Tuning Manager could not be established. (host
name = host-name, agent host name = agent-hostname, agent name = agentname)) See
the cause message. (KAIC15633-E)
messages:
Unable to collect information from Tuning Manager. (host name = host-name, agent
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
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)
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.
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
In addition, if an Agent instance has already started, the following message will be output to a log
file.
Action to be taken:
Upgrade the microcode version of the monitored storage system to a supported version.
1 pmmcChkSvpTrace[n].log The following stack trace will be output together with an error message
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.
1 pmmcChkSvpTrace[n].log The following stack trace will be output together with an error message
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.
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.
In Ver.7
In Ver.7.1
In Ver.8
Appendix1_V8_metri
cs.zip
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
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
End
Restarting the OS
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.
- If you are using a 64-bit OS, substitute the following folders and registry keys for the
corresponding notations used in the text.
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.
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
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.1.1 Terms
The following terms are used in this section.
# Terms 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.
a) Open a command prompt, and then move to the directory indicated below.
# Directory
If the hcmdssrv command does not exist, go to step (1) d) in section 3-b.5.1.2.
# Command
1 hcmdssrv /stop
# Command
1 hcmdssrv /status
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.
# 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.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)
Note: Depending on the uninstallation status, some services might not be
displayed.
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.
Example of the output
Host Name ServiceID Service Name PID Port Status
(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.
Note: The startup type will already be set to Manual for some services.
# 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.
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 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.
If the hcmdscancel command does not exist, go to step (4) in section 3-b.5.1.3.
# Command
1 hcmdscancel TuningManager
# File Name
1 %SystemDrive%\htmpruninst.rtn
(1) Execute the Collection Manager uninstaller (in Windows Server 2003).
a) Open a command prompt.
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.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
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.
(2) Execute the Collection Manager uninstaller (in Windows Server 2008).
a) Open a command prompt.
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.
d) Use the registry editor to make sure that the registry key indicated below
exists.
If this registry key does not exist, go to section 3-b.5.1.5.
# Registry Key
216 Hitachi Proprietary Information
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
<Collection Manager-GUID>
b) Start the registry editor and make sure that the registry key indicated below
exists.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
d) Paste the copied value into the command prompt window, and then execute this
command to start the uninstallation.
b) Start the registry editor and make sure that the registry key indicated below
exists.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{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.
# Command to execute
1 {UninstallString-value}/NOREBOOTNOFLAGOFF (: a single-byte space)
Note: Make sure that the Services applet is closed when executing the uninstaller.
e) Open the following file and make sure that the termination status has been
output.
If the termination status has been output, the uninstallation has finished. Ignore
any other output values.
# File Name
1 %SystemDrive%\htmpruninst.rtn
Note: If the file does not exist, the uninstallation is still in progress.
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
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.
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.
(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
(2) Delete the component install temporary directories that are shared by Hitachi
Storage Command Suite.
# Directory
1 %temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
2 %SystemDrive%\_HDBInstallerTemp
# 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
(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 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.
Make sure that the directories indicated below do not exist. If these directories
exist, delete them manually.
# Directory
1 <Installation directory>
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.
a) Open a command prompt, and then move to the directory indicated below.
# Directory
1 Hitachi Storage Command-Suite-Common-Component-installation-directory\bin
# 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
# 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)
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.1 Terms
The following terms are used in this section.
# Terms 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
# 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
KAVE06008-I The service will now stop. (service=Action Handler)
KAVE06008-I The service will now stop. (service=Trap Generator)
KAVE06008-I The service will now stop. (service=Correlator)
KAVE06008-I The service will now stop. (service=Master Store)
KAVE06008-I The service will now stop. (service=Master Manager)
KAVE06008-I The service will now stop. (service=Name Server)
KAVE06008-I The service will now stop. (service=Status Server)
Note: Depending on the uninstallation status, some services might not be displayed.
f) Execute the command indicated below and make sure that Inactive* is displayed for the
displayed services, as shown in the output example below.
If the jpcctrl command does not exist, go to step (2) in section 3-b.5.2.2.
Even if Inactive* is not displayed (and another string, such as Active, is displayed instead),
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.
Example of the output
Host Name ServiceID Service Name PID Port Status
Note: Depending on the uninstallation status, some services might not be displayed.
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.
# 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
1 Hitachi Storage Command-Suite-Common-Component-installation-directory\bin
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 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
1 hcmdscancel TuningManager
# File Name
1 %SystemDrive%\htmpruninst.rtn
(1) Execute the Collection Manager uninstaller (in Windows Server 2003).
a) Open a command prompt.
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
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
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.
(2) Execute the Collection Manager uninstaller (in Windows Server 2008).
a) Open a command prompt.
1 Hitachi-Tuning-Manager-installation-directory\inst\cm_guid.dat
From the Start menu, choose Run. In the displayed dialog box, enter regedit, and then click the
OK button to start the registry editor.
d) Use the registry editor to make sure that the registry key indicated below exists.
If this registry key does not exist, go to step (3) in section 3-b.5.2.4.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
<Collection Manager-GUID>
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
Note: If the uninstallation terminates successfully, the following dialog box indicating such
is displayed. Click OK to close the dialog box.
Because no windows are displayed during an uninstallation, no user responses are required.
# 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
second to last character is a zero.)
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
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
15
Application\PFM-HealthCheck
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
16
{ADCC02AB-FDA9-4493-9883-7C68AEE4FE70}
Note: If other Hitachi Storage Command Suite products have been installed, the registry
key name Hitachi might be displayed as HITACHI (in all upper-case letters).
b) Make sure that the shared files indicated below do not exist.
b) Start the registry editor and make sure that the registry key indicated below exists.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
d) 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.
a) Make sure that the registry keys indicated below do not exist.
# Registry Key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
1
HiCommandTuningService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\
2
HTM-Tuning Service
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
3
{89331AB6-2E76-4986-9458-54795EF060A0}
b) Start the registry editor and make sure that the registry key indicated below exists.
If this registry key does not exist, go to step (2) in section 3-b.5.2.6.
# Registry Key
d) Paste the copied value into the command prompt window, and then execute this command
with the option shown below to start the uninstallation.
# Command to execute
1 {UninstallString-value}/NOREBOOTNOFLAGOFF (: a single-byte space)
Note: Make sure that the Services applet is closed when executing the uninstaller.
e) Open the following file and make sure that the termination status has been output.
If the termination status has been output, the uninstallation has finished. Ignore any other output
values.
# File Name
1 %SystemDrive%\htmpruninst.rtn
Note: If the file does not exist, the uninstallation is still in progress.
(2) Make sure that the registry keys indicated below do not exist.
a) Make sure that the registry keys indicated below do not exist.
# Registry Key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
1
PerformanceReporter
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
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).
a) Copy the command indicated below to the root directory of the OS startup drive.
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.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.
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
HiCommand Base
HiRDBEmbeddedEdition_HD0
2
(When x64 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\
HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3
HBaseStgMgmtComService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
4
HBaseStgMgmtWebService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
5
HBaseStorageMgmtWebSSOService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
7
HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
8
Application\HBase Storage Mgmt Log
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
9
Application\HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
10
Application\HitachiWebServer
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
11
{1345FCD1-713E-4449-8F76-3F6503941040}
Note: If other Hitachi Storage Command Suite products have been installed, the registry key
name Hitachi might be displayed as HITACHI (in all upper-case letters).
# Directory
1 %temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
2 %SystemDrive%\_HDBInstallerTemp
# 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
(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.
a) Make sure that the directories indicated below do not exist. If these directories exist, delete
them manually.
# Directory
1 <Installation directory>
a) Make sure that the registry keys indicated below do not exist.
# Registry Key
(When x86 is applied) HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
3
Application\TuningManager
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
4
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
5
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
Note: If other Hitachi Storage Command Suite products have been installed, the registry key
name Hitachi might be displayed as HITACHI (in all upper-case letters).
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.
# Directory
1 Hitachi Storage Command-Suite-Common-Component-installation-directory\bin
# 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
Primary Server : 127.0.0.1
Product Name :
DeviceManager
ProvisioningManager
TuningManager
# Command line
hcmdsintg /delete /type TuningManager /user "htnmrepuser" /pass
1
"INTERNALHRXJIHVZ" ( represents a one-byte space)
# Command line
hcmdsintg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ" (
1
represents a one-byte space)
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-d Deleting Tuning Manager server for Solaris (In Ver.6.0.0 to earlier than 8.0.0)
3-d.1 Purpose
This appendix provides an overview of deleting Tuning Manager server for Solaris, and describes
the following procedures (which are not disclosed to users):
- Procedure for deleting Tuning Manager server without deleting Agent
- Procedure for forcibly deleting the Tuning Manager server manually
Is the No
Yes /tmp/hcmdsrtn.enf
value 0?
Deleting the OS settings
END Yes
Restarting the OS
Deleting packages
Restarting the OS
END
Figure 3-d.3-1 The flow of the deletion of the Tuning Manager server
- Only perform the forced deletion procedure described in section 3-d.5 if you cannot perform a
normal uninstallation.
- Before you forcibly delete Tuning Manager server, make sure that Hitachi Storage Command
Suite family of products other than Tuning Manager server have not been installed. If such
products have been installed, uninstall them before forcibly deleting Tuning Manager server.
For details about how to uninstall a HiCommand product, see the maintenance manual or other
manuals for the product.
- The deletion procedure described in this document does not change the settings of Hitachi
Storage Command Suite family of products (including Agents), such as HiCommand Device
Manager, that are installed on hosts other than the host on which Tuning Manager server is
installed. To change the settings of such products, see the maintenance manual or other manuals
for the products.
1 $CM_NOUNINST 1
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.
Output results
KAPM06441-I The HiRDB service has already stopped.
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Web Service
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Common Service
KAPM05009-I Already stopped service. service-name=HiCommand Suite TuningManager
KAPM05009-I Already stopped service. service-name=HiCommand Suite TuningService
KAPM05009-I Already stopped service. service-name=HiCommand Performance Reporter
If the service statuses are not the same as those indicated in the above output results 10 minutes
after performing step (1), restart the OS, and then perform step (1) again. If the services still
have not stopped, go to section 3-d.5.2.
Depending on the status after uninstallation, some services might no longer exist. In this case,
make sure that all the displayed services have stopped.
3-d.5.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
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:
# Environment Value
variable name
1 PDDIR /opt/HiCommand/Base/HDB
2 PDCONFPATH /opt/HiCommand/Base/HDB/conf
3 LD_LIBRARY_PATH /opt/HiCommand/Base/HDB/lib
(3) Execute the following command to confirm that a pdprcd process is running.
# Command
1 ps ef |grep pdprcd
(b) In these files, check the values of the properties indicated below, which indicate the
database file directories. Note that the db_areapath2 property might not be specified in the
file.
# File Name
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).
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
If the pkgrm command fails, delete the directory indicated below. If the package has been
246 Hitachi Proprietary Information
uninstalled and the directory no longer exists, go to the next step.
# Directory
1 /var/sadm/pkg/HTMCD2
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
# Directory
1 /var/sadm/pkg/HTMPR
If the pkgrm command fails, delete the directory indicated below. If the package has been
uninstalled and the directory no longer exists, go to the next step.
# Directory
1 /var/sadm/pkg/HTMTsvc
If the pkgrm command fails, delete the directory indicated below. If the package has been
uninstalled and the directory no longer exists, go to the next step.
# Directory
1 /var/sadm/pkg/HBASE
Execute the following commands to delete installed information, and then terminate the
commands.
# Command
1 /etc/hitachi_setup
2 /etc/hitachi_x64setup
Use the following command to check the number of products that have been installed.
# Command
1 /etc/.hitachi/bin/SHOWPP
# Files
1 /etc/hitachi_start
2 /etc/hitachi_setup
3 /etc/hitachi_x64setup
# Command line
1 hcmdsintg -print -user "htnmrepuser" -pass " INTERNAL HRXJIHVZ"
3-e Force uninstall of the Tuning Manager agents for Windows (In Ver.6.0.0 to earlier
than 8.0.0)
3-e.1 Purpose
This is the procedure for how to delete the agents (Windows) of Hitachi Tuning Manager in force.
Start
Yes
Stop the agent related service
Reboot the OS
Both conditions
No
in (*1) met?
Yes
Reboot the OS
Figure 3-e.4-1 The flow of the deletion of the agent and re-install the agent
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.
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.
(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
# 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.
Specify the directory path got in the chapter 3-e.6.2 (1) as the <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.
2 Windows Server 2003 x64 Including R2.
3 Windows Server 2003 IPF -
4 Windows Server 2008 x86 -
5 Windows Server 2008 x64 Including R2.
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
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
<Windows (x64)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
(1) Start a command prompt. If the UAC function is being used in Windows Server 2008, start an
elevated command prompt that has administrator privileges.
# Command
1 htnmagtregclean
(4) Check the end code that appears in the command prompt in response to the htnmagtregclean
command.
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.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
<Windows (x64)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
3-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
Yes
Delete the file/directory
Reboot the OS
End
Figure 3-f.4-1 The flow of the deletion of the agent and re-install the agent
- In Ver.6
Hitachi Tuning Manager Software Installation Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Installation Guide
If the attempt for uninstalling the agent successfully ends, then following message that indicates
the completion of uninstall is shown.
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.
(b) Linux
# File
1 Files in /etc/init.d whose names begin with hicommand-
2 Files in /etc/rc3.d whose names begin with K99hicommand-
3 Files in /etc/rc3.d whose names begin with S99hicommand-
4 Files in /etc/rc5.d whose names begin with K99hicommand-
5 Files in /etc/rc5.d whose names begin with S99hicommand-
Is the No
Yes /tmp/hcmdsrtn.enf
value 0?
Deleting the OS settings
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
- Only perform the forced deletion procedure described in section 3-g.5 if you cannot perform a
normal uninstallation.
- Before you forcibly delete Tuning Manager server, make sure that Hitachi Storage Command
Suite family of products other than Tuning Manager server have not been installed. If such
products have been installed, uninstall them before forcibly deleting Tuning Manager server.
For details about how to uninstall a HiCommand product, see the maintenance manual or other
manuals for the product.
- The deletion procedure described in this document does not change the settings of Hitachi
Storage Command Suite family of products (including Agents), such as HiCommand Device
Manager, that are installed on hosts other than the host on which Tuning Manager server is
installed. To change the settings of such products, see the maintenance manual or other manuals
for the products.
1 $CM_NOUNINST 1
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.
Output results
KAPM06441-I The HiRDB service has already stopped.
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Web Service
KAPM05009-I Already stopped service. service-name=HBase Storage Mgmt Common Service
KAPM05009-I Already stopped service. service-name=HiCommand Suite TuningManager
KAPM05009-I Already stopped service. service-name=HiCommand Performance Reporter
If the service statuses are not the same as those indicated in the above output results 10 minutes
after performing step (1), restart the OS, and then perform step (1) again. If the services still
have not stopped, go to section 3-g.5.2.
Depending on the status after uninstallation, some services might no longer exist. In this case,
make sure that all the displayed services have stopped.
name
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>/conf/hcmdsdbinit.ini initpath
1 /var<Hitachi-Command-Suite-Common-Component-Installation-directory>/tmp/HBuninst.sh
2 <Hitachi-Command-Suite-Common-Component-Installation-directory> (including
subdirectories)
5 /var<Hitachi-Command-Suite-Common-Component-Installation-directory> (including
subdirectories)
3-g.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 <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin/
2 ./hcmdscancel PerformanceReporter
3 ./hcmdscancel TuningManager
1 cd <directory-to-which-HBuninst.sh-has-been-copied>
2 ./HBuninst.sh /X
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:
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.
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
12 /etc/rc3.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
13 /etc/rc5.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
14 /etc/rc6.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
# 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
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-dire
ctory>/HDB/lib
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
HDB
ctory>/HDB/conf
on-directory>/HDB/lib
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdstop f
(3) Execute the following command to confirm that a pdprcd process is running.
# Command
1 ps ef |grep pdprcd
1 kill 9 <pdprcd-process-number>
Note: You can use the ps command to check the process number (PID) of pdprcd.
1 <TuningManager-Installation-directory>/inst/db_area.properties
(b) In these files, check the values of the properties indicated below, which indicate the
database file directories. Note that the db_areapath2 property might not be specified in the
file.
# File Name
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).
1 rpm -e HTNM
1 rpm e HTMPR
2 /var<TuningManager-Installation-directory>
3 <Hitachi-Command-Suite-Common-Component-Installation-directory>
4 /var<Hitachi-Command-Suite-Common-Component-Installation-directory>
5 /opt/jp1pc
6 /etc/.hitachi/HBase
7 /etc/.hitachi/HTNM
Execute the following commands to delete installed information, and then terminate the
commands.
# Command
1 /etc/hitachi_setup
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.
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
1 /etc/hitachi_start
2 /etc/hitachi_setup
d) Execute the command indicated below. Make sure that TuningManager is not included in
the output results.
# Command line
1 hcmdsintg -print -user "htnmrepuser" -pass " INTERNAL HRXJIHVZ"
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".
Start
Forcibly Deleting Tuning Manager server
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
End
Delete HiCommand Device Manager authentication information
End
End
Notes:
- On a host on which Tuning Manager server and Agent are installed, if you want to delete only
Tuning Manager server, use the deletion procedure described in 3-h.4. Do not use the forced
deletion procedure described in 3-h.5. If you do, all Hitachi Command Suite (incluFile Services
Manager or Storage Navigator Modular2) products, including Agent, will no longer start.
- Only perform the forced deletion procedure described in section 3-h.5 if you cannot perform a
normal uninstallation.
- Before you forcibly delete Tuning Manager server, make sure that Hitachi Command Suite
family (including Hitachi File Services Manager and Hitachi Storage Navigator Modular 2) of
products other than Tuning Manager server have not been installed. If such products have been
installed, uninstall them before forcibly deleting Tuning Manager server. For details about how
to uninstall a Hitachi Command Suite product, see the maintenance manual or other manuals
for the product.
- Because the forced deletion procedure edits the registry, special care is required.
- The deletion procedure described in this document does not change the settings of Hitachi
Command Suite family (including Agents, Hitachi File Services Manager and Hitachi Storage
Navigator Modular 2) of products (including Agents), such as HiCommand Device Manager,
that are installed on hosts other than the host on which Tuning Manager server is installed. To
change the settings of such products, see the maintenance manual or other manuals for the
products.
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.
Uninstall Tuning Manager server. When Tuning Manager server is successfully uninstalled, the
following window appears.
277 Hitachi Proprietary Information
Figure 3-h.4-1: Window that appears when Tuning Manager server is successfully uninstalled
Make sure that no value has been specified for the following environment variable.
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.
Notes:
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
installation directory during a new installation. If the installation directory was changed from the default, use
3-h.5.1.1 Terms
The following terms are used in this section.
# Terms Directory
1 Suite-Common-Component-installation-d
irectory
Note1: Unless you specify other directories during installation, the above directories are
used by default.
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.
a) Open a command prompt, and then move to the directory indicated below.
# Directory
If the hcmds64srv command does not exist, go to step (1) d) in section 3-h.5.1.2.
# Command
1 hcmds64srv /stop
c) Execute the following command and make sure that stopped is displayed for the displayed
services, as shown in the output example below.
# Command
1 hcmds64srv /status
KAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt Web SSO Service
Note: Depending on the uninstallation status, some services might not be displayed.
Note: If stopped is still not displayed for hcmds64srv /status 10 minutes after executing
hcmds64srv /stop, go to step (1) d) in section 3-h.5.1.2.
# 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
Output example
KAVE06008-I The service will now stop. (service=Action Handler)
KAVE06008-I The service will now stop. (service= Agent for HealthCheck)
KAVE06008-I The service will now stop. (service= Agent Store for HealthCheck)
KAVE06008-I The service will now stop. (service= View Server)
KAVE06008-I The service will now stop. (service=Trap Generator)
KAVE06008-I The service will now stop. (service=Correlator)
KAVE06008-I The service will now stop. (service=Master Store)
KAVE06008-I The service will now stop. (service=Master Manager)
KAVE06008-I The service will now stop. (service=Name Server)
KAVE06008-I The service will now stop. (service=Status Server)
Note: Depending on the uninstallation status, some services might not be displayed.
f) Execute the command indicated below and make sure that Inactive* is displayed for the
displayed services, as shown in the output example below.
If the jpcctrl command does not exist, go to step (2) in section 3-h.5.1.2.
Even if Inactive* is not displayed (and another string, such as Active, is displayed instead),
go to step (2) in section 3-h.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.
Example of the output
Host Name ServiceID Service Name PID Port Status
Note: Depending on the uninstallation status, some services might not be displayed.
(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.
Note: The startup type will already be set to Manual for some services.
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.
(1) Check the directory that stores the database for Hitachi Command Suite Common Component.
# File Name
1 Hitachi 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
1 Hitachi Command Suite-Common-Component-installation-directory\bin
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 any error message displayed except KAPM04118-E, wait about 10 seconds, then re-execute
the command. If the error messages still remain after re-execution three times, go to step (3) in
section 3-h.5.1.3.
If the hcmdscancel command does not exist, go to step (4) in section 3-h.5.1.3.
# Command
1 hcmdscancel TuningManager
# File Name
1 %SystemDrive%\htmpruninst.rtn
If the file does not exist, go to section 3-h.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-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.
Note: If the uninstallation terminates successfully, the following dialog box indicating such
is displayed. Click OK to close the dialog box.
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-h.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-h.5.1.12.
b) Start the registry editor and make sure that the registry key indicated below exists.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
d) 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.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{465EF71F-B608-4
C33-9E19-D56DDCADC82A}
b) Start the registry editor and make sure that the registry key indicated below exists.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninst
all\{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.
# Command to execute
1 {UninstallString-value}/NOREBOOTNOFLAGOFF (: a single-byte space)
Note: Make sure that the Services applet is closed when executing the uninstaller.
e) Open the following file and make sure that the termination status has been output.
If the termination status has been output, the uninstallation has finished. Ignore any other output
values.
# File Name
1 %SystemDrive%\htmpruninst.rtn
Note: If the file does not exist, the uninstallation is still in progress.
287 Hitachi Proprietary Information
Note: Uninstallation might take five or more minutes to finish.
(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.
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 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) Forcibly deleting the 64-bit version of Hitachi Command Suite Common Component
a) Copy the command indicated below to the directory of the OS system drive. If the file does not
exist, go to section 3-h.5.1.8.
If you forcibly deleted the 32-bit version of Hitachi Command Suite Common Component, a
file with the same name might exist in the copy destination. In such a case, be sure to overwrite
the file.
# File
To earlier than Ver.8.1
%SystemDrive%\Program Files\HiCommand\Base64\tmp\HBuninst.exe
1
Ver.8.1 or later
%SystemDrive%\Program Files\HiCommand\Base64\tmp\HB64uninst.exe
Note:
The above directory is the default installation directory of the 64-bit version of Hitachi
Command Suite Common Component.
b) Open a command prompt, and then move to the directory of the OS system drive.
c) Execute the command indicated below. Respond to all questions with Yes.
# Command line
To earlier than Ver.8.1
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.
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.
(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.
(2) Delete the component install temporary directories that are shared by Hitachi Command Suite.
If the following directories exist, delete them manually.
# Directory
1 %temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
2 %SystemDrive%\_HDBInstallerTemp
# 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.
(4) Delete the database files used by Hitachi Command Suite Common Component.
292 Hitachi Proprietary Information
In an environment in which an upgrade from version 7 or earlier has been performed, you also
need to perform the steps shown below in the old environment (version 7 or earlier)
Delete the directory you wrote down in step (1) of section 3-h.5.1.3.
If 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.
# Directory
1 <Installation directory>
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.
a) Open a command prompt, and then move to the directory indicated below.
# Directory
1 Hitachi Command Suite-Common-Component-installation-directory\bin
# Command line
hcmds64intg /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-h.5.1.12.
Output example
Primary Server : 127.0.0.1
Product Name :
DeviceManager
TuningManager
# Command line
hcmds64intg /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
hcmds64intg /print /user "htnmrepuser" /pass "INTERNALHRXJIHVZ" (
1
represents a one-byte space)
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-h.5.2.1 Terms
The following terms are used in this section.
# Terms Directory
1 Suite-Common-Component-installation-dir
ectory
Note1: Unless you specify other directories during installation, the above directories are
used by default.
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.
a) Open a command prompt, and then move to the directory indicated below.
# Directory
If the hcmds64srv command does not exist, go to step (1) d) in section 3-h.5.2.2.
# Command
1 hcmds64srv /stop
c) Execute the following command and make sure that stopped is displayed for the displayed
services, as shown in the output example below.
# Command
1 hcmds64srv /status
KAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt Web SSO Service
Note: Depending on the uninstallation status, some services might not be displayed.
Note: If stopped is still not displayed for hcmds64srv /status 10 minutes after executing
hcmds64srv /stop, go to step (1) d) in section 3-h.5.2.2.
# 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
If the message KAVE05000-E The specified service is not running is displayed, the service is
not running, so go to the next step.
Output example
KAVE06008-I The service will now stop. (service=Action Handler)
KAVE06008-I The service will now stop. (service= Agent for HealthCheck)
296 Hitachi Proprietary Information
KAVE06008-I The service will now stop. (service= Agent Store for HealthCheck)
KAVE06008-I The service will now stop. (service= View Server)
KAVE06008-I The service will now stop. (service=Trap Generator)
KAVE06008-I The service will now stop. (service=Correlator)
KAVE06008-I The service will now stop. (service=Master Store)
KAVE06008-I The service will now stop. (service=Master Manager)
KAVE06008-I The service will now stop. (service=Name Server)
KAVE06008-I The service will now stop. (service=Status Server)
Note: Depending on the uninstallation status, some services might not be displayed.
f) Execute the command indicated below and make sure that Inactive* is displayed for the
displayed services, as shown in the output example below.
If the jpcctrl command does not exist, go to step (2) in section 3-h.5.2.2.
Even if Inactive* is not displayed (and another string, such as Active, is displayed instead),
go to step (2) in section 3-h.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.
Example of the output
Host Name ServiceID Service Name PID Port Status
Note: Depending on the uninstallation status, some services might not be displayed.
(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
297 Hitachi Proprietary Information
services. You can change the startup type from the Service Properties dialog box.
Note: Depending on the uninstallation status in section 3-h.4, some services might not be
displayed.
Note: The startup type will already be set to Manual for some services.
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.
(1) Check the directory that stores the database for Hitachi Command Suite Common Component.
# File Name
1 Hitachi 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
1 Hitachi Command Suite-Common-Component-installation-directory\bin
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 hcmdscancel command does not exist, go to step (4) in section 3-h.5.2.3.
# Command
1 hcmdscancel TuningManager
# File Name
1 %SystemDrive%\htmpruninst.rtn
# File Name
1 Hitachi-Tuning-Manager-installation-directory\inst\cm_guid.dat
From the Start menu, choose Run. In the displayed dialog box, enter regedit, and then click the
OK button to start the registry editor.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
<Collection Manager-GUID>
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersio
n\Uninstall\<Collection Manager-GUID>
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
Note: If the uninstallation terminates successfully, the following dialog box indicating such
is displayed. Click OK to close the dialog box.
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.
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
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.)
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.
b) Start the registry editor and make sure that the registry key indicated below exists.
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
{89331AB6-2E76-4986-9458-54795EF060A0}
d) 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.
a) Make sure that the registry keys indicated below do not exist.
# Registry Key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
1
HiCommandTuningService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\
2
HTM-Tuning Service
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
3
{89331AB6-2E76-4986-9458-54795EF060A0}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{465EF71F-B608-4C33-
9E19-D56DDCADC82A}
b) Start the registry editor and make sure that the registry key indicated below exists.
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}
d) Paste the copied value into the command prompt window, and then execute this command
with the option shown below to start the uninstallation.
# Command to execute
1 {UninstallString-value}/NOREBOOTNOFLAGOFF (: a single-byte space)
Note: Make sure that the Services applet is closed when executing the uninstaller.
e) Open the following file and make sure that the termination status has been output.
If the termination status has been output, the uninstallation has finished. Ignore any other output
values.
# File Name
1 %SystemDrive%\htmpruninst.rtn
Note: If the file does not exist, the uninstallation is still in progress.
(2) Make sure that the registry keys indicated below do not exist.
a) Make sure that the registry keys indicated below do not exist.
# Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\
3
{465EF71F-B608-4C33-9E19-D56DDCADC82A}
In an environment in which an upgrade from version 7 or earlier has been performed, you
also need to perform the procedures described in this section for version 7.
# Registry Key
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}
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).
(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
b) Open a command prompt, and then move to the directory of the OS system drive.
c) Execute the command indicated below. Respond to all questions with Yes.
# 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).
(2) Forcibly deleting the 64-bit version of Hitachi Command Suite Common Component
a) Copy the command indicated below to the directory of the OS system drive. If the file does not
exist, go to step (3).
If you forcibly deleted the 32-bit version of Hitachi Command Suite Common Component, a
file with the same name might exist in the copy destination. In such a case, be sure to overwrite
the file.
# 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:
The above directory is the default installation directory of the 64-bit version of Hitachi
Command Suite Common Component.
b) Open a command prompt, and then move to the directory of the OS system drive.
c) Execute the command indicated below. Respond to all questions with Yes.
# Command line
To earlier than Ver.8.1
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 hcmds64rtn.enf
If the value is 2, restart the OS, and then re-execute the command described in step (2) c).
If the value is not 2, or if the value is still 2 after re-execution, restart the OS, and then go to step
(3).
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.
HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\
2
HiRDBEmbeddedEdition_HD1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3
HBase64StgMgmtWebService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
4
HBase64StgMgmtSSOService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
5
HBase64StgMgmtWebSSOService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
6
HiRDBEmbeddedEdition_HD1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\
7
HBase64 Event
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\
8
HBase64 Storage Mgmt Log
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\
9
HiRDBEmbeddedEdition_HD1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
10
{1345FCD1-713E-4449-8F76-3F6503941040} (*1)(*2)
In an environment in which an upgrade from version 7 or earlier has been performed, you
307 Hitachi Proprietary Information
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.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\
2
HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3
HBaseStgMgmtComService
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
4
HiRDBClusterService_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
5
HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
6
Application\HBase Storage Mgmt Log
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
7
Application\HiRDBEmbeddedEdition_HD0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
8
Application\HitachiWebServer
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
9
{1345FCD1-713E-4449-8F76-3F6503941040} (*1) (*2)
*2: The value of the registry key of HiRDB is changed for every installation. Therefore, check
a value by the following methods.
V8.0.0 or later
Check the value in "Value data" for the InstallGuid value in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\
HiRDBEmbeddedEdition_HD1\<CurrentVersion>
<CurrentVersion> is equal to the value in "Value data" for the CurrentVersion value
in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\HiRDBEmb
eddedEdition_HD1.
Note: If other Hitachi Command Suite products have been installed, the registry key name
Hitachi might be displayed as HITACHI (in all upper-case letters).
# Directory
1 %temp%\{1345FCD1-713E-4449-8F76-3F6503941040}
2 %SystemDrive%\_HDBInstallerTemp
# 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
c) Delete the directories specified as the values of the db_areapath1 and db_areapath2
properties.
(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.
a) Make sure that the directories indicated below do not exist. If these directories exist, delete
them manually.
# Directory
1 <Installation directory>
a) Make sure that the registry keys indicated below do not exist.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
2
HiCommandTuningManager64
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3
TuningManagerRESTService
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
4
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
5
{7CD2AAA1-4E2E-4797-AA49-7037FF4EDBCA}
Note: If other Hitachi Command Suite products have been installed, the registry key name
Hitachi might be displayed as HITACHI (in all upper-case letters).
In an environment in which an upgrade from version 7 or earlier has been performed, you
also need to perform the steps shown below in the old environment (version 7 or earlier)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\
2
Application\TuningManager
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
3
{61577C30-8F2D-445E-9E9F-54F65EE419A5}
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)
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 HiCommand Device Manager.
a) Open a command prompt, and then move to the directory indicated below.
# Directory
1 Hitachi Command Suite-Common-Component-installation-directory\bin
# Command line
hcmds64intg /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-h.5.2.12.
Output example
Primary Server : 127.0.0.1
Product Name :
DeviceManager
TuningManager
# Command line
hcmds64intg /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
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.
Restarting the OS
Deleting packages
Restarting the OS
END
Figure 3-i.3-1 The flow of the deletion of the Tuning Manager server
- Only perform the forced deletion procedure described in section 3-i.5 if you cannot perform a
normal uninstallation.
- Before you forcibly delete Tuning Manager server, make sure that Hitachi Command Suite
family (including Hitachi File Services Manager and Hitachi Storage Navigator Modular 2) of
products other than Tuning Manager server have not been installed. If such products have been
installed, uninstall them before forcibly deleting Tuning Manager server. For details about how
to uninstall a HiCommand product, see the maintenance manual or other manuals for the
product.
- The deletion procedure described in this document does not change the settings of Hitachi
Command Suite family (including Hitachi File Services Manager and Hitachi Storage
Navigator Modular 2) of products (including Agents), such as HiCommand Device Manager,
that are installed on hosts other than the host on which Tuning Manager server is installed. To
change the settings of such products, see the maintenance manual or other manuals for the
products.
1 $CM_NOUNINST 1
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.
# Command
1 cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
2 ./hcmdssrv stop
(2) Execute the following command and make sure that all the services indicated in the output
results have stopped.
# Command
1 ./hcmds64srv status
Output results
KAPM06441-I The HiRDB service has already stopped.
KAPM05009-I Already stopped service. service-name=HBase 64 Storage Mgmt Web SSO Service
If the service statuses are not the same as those indicated in the above output results 10 minutes
after performing step (1), restart the OS, and then perform step (1) again. If the services still
have not stopped, go to section 3-i.5.2.
Depending on the status after uninstallation, some services might no longer exist. In this case,
make sure that all the displayed services have stopped.
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
In an environment that satisfies any of the conditions listed below, two different instances of Hitachi
Command Suite Common Component (for 32bit OS and for 64bit OS) might be installed:
- Hitachi Command Suite version 7 or earlier is currently installed or was previously installed.
- File Services Manager is currently installed or was previously installed.
- Storage Navigator Modular 2 is currently installed or was previously installed.
(1) Forcibly deleting the 32-bit version of Common Component and HiRDB
The installation directory of the 32-bit version of Common Component is shown below. Note
that this is the default directory path.
# Hitachi Command Suite Common Component Installation directory
1 /opt/HiCommand/Base
1 cd <HBase32-Installation-directory>/bin/
2 ./hcmdscancel PerformanceReporter
3 ./hcmdscancel TuningManager
b) Copy the file indicated below to a valid directory. If this file does not exist, go to step (2) in
this section.
# File to copy
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
1 cd <directory-to-which-HBuninst.sh-has-been-copied>
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.
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:
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.
Restart the OS, and then perform step (1) c) in this section.
1
Regardless of the execution results, go to step (2) in this section.
2 Go to step (2) in this section.
(2) Forcibly deleting the 64-bit version of Common Component and HiRDB
The installation directory of the 64-bit version of Common Component is shown below. Note
that this is the default directory path.
# Hitachi Command Suite Common Component Installation directory
1 /opt/HiCommand/Base64
1 cd <HBase64-Installation-directory>/sbin/
2 ./hcmdscancel PerformanceReporter
3 ./hcmdscancel TuningManager
b) Copy the file indicated below to a valid directory. If this file does not exist, go to step (3) in
this section.
# File to copy
# 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
1 cd <directory-to-which-HBuninst.sh/HB64uninst.sh-has-been-copied>
Ver.8.1 or later
./HB64uninst.sh /X
Note:
/X is an option, not a directory.
If the Hitachi Command Suite services are active during the command execution, restart the
OS, and then re-execute the commands.
When you execute the command, the message indicated under "Output result 1" is output. Enter
Yes for this message.
Output result 1
KAPM04315-W All the files for HBASE will now be deleted. Is this OK? Yes/No:
The message indicated under "Output result 2" is output. Enter Yes for this message
Output result 2
KAPM04316-W Are you sure you want to delete all of the files? Yes/No:
1 /tmp/hcmds64rtn.enf
i) If the value is 0:
321 Hitachi Proprietary Information
Go to step (3) in this section.
ii) If the value is 1:
Restart the OS, and then perform step (2) c) in this section.
Regardless of the execution results, go to step (3) in this section.
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
0 Go to step (3) in this section.
Restart the OS, and then perform step (2) c) in this section.
1
Regardless of the execution results, go to step (3) in this section.
2 Go to step (3) in this section.
(3) Checking the deletion status of Hitachi Command Suite Common Component
If you performed only step (2), perform the steps in the following table.
Condition Subsequent action
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
(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
322 Hitachi Proprietary Information
/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
6 /etc/init.d/HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
7 /etc/rc0.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
8 /etc/rc1.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
9 /etc/rc2.d/S07HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
10 /etc/rc3.d/S07HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
11 /etc/rc5.d/S07HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
12 /etc/rc6.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
[RHEL]
Delete the following files.
# File
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
10 /etc/rc1.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
11 /etc/rc2.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
12 /etc/rc3.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
13 /etc/rc5.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
14 /etc/rc6.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.HDB
(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
iii.
Delete the following files if the above command fails.
# File
[RHEL]
Delete the following files.
# File
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
11 /etc/rc1.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
12 /etc/rc2.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
13 /etc/rc3.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
14 /etc/rc5.d/S91HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
HDB
15 /etc/rc6.d/K09HiRDB_E.<Hitachi-Command-Suite-Common-Component-Installation-directory>.Base64.
NOTE:
If Hitachi Command Suite Common Component is installed in the default location,
<Base-installation-directory> is replaced with "opt.HiCommand.Base64".
If Hitachi Command Suite Common Component is installed in a location other than the default,
<Base-installation-directory> is replaced with a name in which "/", which indicates the hierarchy
of the directory specified as the installation directory, is replaced with ".".
In an environment in which an upgrade from version 7 or earlier has been performed, you also
need to perform the steps shown below in the old environment (version 7 or earlier).
[RHEL7.x, SUSE12]
Delete the following entries that were added to /etc/inittab, if exist them.
Entries to delete
penn: < number
>:wait:<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/etc/pdpwon_e
PDnn: < number
>:respawn:<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdd
PDnn: < number >:respawn: env LD_LIBRARY_PATH=
<Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdd
nn:double digit numbers
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
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
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-dire
ctory>/HDB/lib
export PDDIR
export PDCONFPATH
export LD_LIBRARY_PATH
HDB
ctory>/HDB/conf
on-directory>/HDB/lib
1 <Hitachi-Command-Suite-Common-Component-Installation-directory>/HDB/bin/pdstop f
(3) Execute the following command to confirm that a pdprcd process is running.
# Command
1 ps ef |grep pdprcd
1 kill 9 <pdprcd-process-number>
Note: You can use the ps command to check the process number (PID) of pdprcd.
1 <TuningManager-Installation-directory>/inst/db_area.properties
2 <TuningManager-Installation-directory>/inst/db_area_6.properties
(b) In these files, check the values of the properties indicated below, which indicate the
database file directories. Note that the db_areapath2 property might not be specified in the
file.
# File Name
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).
1 rpm -e HTNM
2 rpm -e htnm-server
1 rpm e HTMPR
2 /var<TuningManager-Installation-directory>
3 <Hitachi-Command-Suite-Common-Component-Installation-directory>
4 /var<Hitachi-Command-Suite-Common-Component-Installation-directory>
5 /opt/jp1pc
6 /etc/.hitachi/HBase
7 /etc/.hitachi/HBase64
8 /etc/.hitachi/HTNM
Execute the following commands to delete installed information, and then terminate the
commands.
# Command
1 /etc/hitachi_setup
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.
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
# 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
[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.
Start
Yes
Stop the agent related service
Reboot the OS
Both conditions
No
in (*1) met?
Yes
Reboot the OS
End
Figure 3-j.4-1 The flow of the deletion of the agent and re-install the agent
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.
(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
(c) Paste the character string of the second line into the command prompt, and then execute the
command. The uninstallation will start.
# Command to execute
1 {UninstallString-command}
<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.
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 -
2 Windows Server 2008 x64 Including R2.
3 Windows Server 2012 x64 Including R2.
# 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
# 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 and
Windows Server 2012, use an elevated command prompt that has administrator privileges to
execute the htnmagtregclean command. Move the mouse pointer over the command prompt
icon, and then right-click it. A context menu appears. From this menu, select Run as
administrator to start an elevated command prompt that has administrator privileges. If you
attempt to use an unelevated command prompt to execute the htnmagtregclean command, the
registry keys might not be deleted.
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.
<Windows (x86)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
<Windows (x64)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
(1) Start a command prompt. If the UAC function is being used in Windows Server 2008 and
Windows Server 2012, start an elevated command prompt that has administrator privileges.
# Command
1 htnmagtregclean
To continue, enter [y] or [Y]. To cancel the command, enter [n] or [N].
(4) Check the end code that appears in the command prompt in response to the htnmagtregclean
command.
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 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.
# Log File
1 %SystemDrive%\htnmagtregclean.log
<Windows (x86)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
<Windows (x64)>
# Registry Key
1 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PC
2 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCMGR
3 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTP
4 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi\JP1PCAGTx
5 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xA_yyyy
6 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCAGT_xS_yyyy
7 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService
(*1) The registry key Hitachi may be shown as large character HITACHI when other Hitachi
product is installed into the same server.
(*2) The character x indicates the agent service key, the characters yyyy indicates the agent
instance name.
# 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
[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.
(*1) Including its bug fix version
Start
Yes
Delete the file/directory
Reboot the OS
End
Figure 3-k.4-1 The flow of the deletion of the agent and re-install the agent
If the attempt for uninstalling the agent successfully ends, then following message that indicates
the completion of uninstall is shown.
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.
# File Name
# Command
1 cd /opt/jp1pc/htnm/bin
2 ./htmsrv stop -all
(c) Execute the following command in the console. The uninstallation will start in the console.
# Command to execute
1 For Linux:
/etc/hitachi_x64setup -f -e -u -t "<Agent Installation
Directory>/htnm/Rest/system/PSB_INST.INF"
(b) Linux
# File
1 Files in /etc/init.d whose names begin with hicommand-
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
4 Files in /etc/rc3.d whose names begin with K99hicommand-
5 Files in /etc/rc3.d whose names begin with S99hicommand-
6 Files in /etc/rc3.d whose names begin with K99htnm_agent_rest
7 Files in /etc/rc3.d whose names begin with S99htnm_agent_rest
8 Files in /etc/rc5.d whose names begin with K99hicommand-
9 Files in /etc/rc5.d whose names begin with S99hicommand-
10 Files in /etc/rc5.d whose names begin with K99htnm_agent_rest
11 Files in /etc/rc5.d whose names begin with S99htnm_agent_rest
12 Files in /etc/rc6.d whose names begin with K01htnm_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
[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".
HiRDB/EmbeddedEdition _HD0
[ In Ver.8 or later ]
HiRDB/EmbeddedEdition _HD1
5. Change current directory to "bin" directory of the install directory of Hitachi Storage Command
Suite Common Component database.
cd <Suite Install-dir>\HDB\BIN
6. Execute the following command. (This command sets the environment variable that is necessary
for executing command of HiRDB. This command needs to be executed on the Command prompt
used in procedure 7.)
pdntcmd
After executing "pdntcmd" command, operate the following procedures a) d), then confirm that the
environment variable is set correctly.
a) Execute "set PATH" command to confirm that the following two paths are added to the result.
<Suite Install-dir>\HDB\BIN
<Suite Install-dir>\HDB\CLIENT\UTL
< When the above paths are not added >
Execute the following command manually to add the path. After executing the command, execute
"set PATH" command and confirm that the paths are added.
set PATH=<Suite Install-dir>\HDB\BIN;<Suite Install-dir>\HDB\CLIENT\UTL;%PATH%
b) Execute "set PDDIR" command and confirm that the result is following.
<Suite Install-dir>\HDB
< When the above character string is not defined in PDDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDDIR" command and confirm that the variable was defined correctly.
set PDDIR=<Suite Install-dir>\HDB
< When the above character string is not defined in PDCONFPATH variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDCONFPATH " command and confirm that the variable was defined correctly.
set PDCONFPATH=<Suite Install-dir>\HDB\CONF
d) Execute "set PDUXPLDIR" command and confirm that the result is following.
<Suite Install-dir>\HDB\UXPLDIR
< When the above character string is not defined in PDUXPLDIR variable >
Execute the following command manually to define the variable. After executing the command,
execute "set PDUXPLDIR" command and confirm that the variable was defined correctly.
set PDUXPLDIR=<Suite Install-dir>\HDB\UXPLDIR
Change current directory to "bin" directory of the install directory of Hitachi Storage Command
Suite Common Component database.
cd <Suite Install-dir>\HDB\BIN
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)
9 CLOSE ACCEPT-HOLD
10 HOLD
[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>.
[Note3] Use absolute path for specifying <Extended directory>. Note that Drive name should
be included in absolute path when OS is Windows.
( ) (For Windows )
Back Slush (For Windows, for specifying the directory relationship between the parent
Slush (For Solaris, for specifying the directory relationship between the parent and the
child directory).
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.
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.
How to set the environmental variable is different between Windows and Solaris.
<Step1> Execute the following command for setting the environmental variable
1 cd /d "<Suite Install-dir>\HDB\bin"
2 pdntcmd
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
# Command
1 set PDDIR
<Step1> Execute the following command for setting the environmental variable
Depending on the type of shell, how to set the environmental variable differs.
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
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
4 Shell other than the above refer to the manual of each shell.
# Command
Display result
PDDIR=/opt/HiCommand/Base/HDB
(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
(b) Create the database log file by executing the following command
# Command
(c) Confirm that database log file is successfully created by executing the following command
# Command
Display result
lg7
# Command
Display result
lg8
# Command
Display result
lg9
# Command
Display result
lg10
Display result
lg11
# Command
Display result
lg12
Windows
<Suite Install-dir>\HDB\CONF
Solaris
/opt/HiCommand/Base/HDB/CONF
iii) Add the following definition at the end of the sds01 file
pdlogadfg -d sys -g log7 ONL
pdlogadfg -d sys -g log8 ONL
pdlogadfg -d sys -g log9 ONL
pdlogadfg -d sys -g log10 ONL
pdlogadfg -d sys -g log11 ONL
pdlogadfg -d sys -g log12 ONL
[Note 1] Change the name of the <Extended directory> into the specified directory name.
iv) Save the contents of sds01 file, and then close the sds01 file.
# Command
1 pdconfchk
Display result
# Command
1 pdlogls -d sys
Display result
HOSTNAME : NUCSTG02(******)
Group Type Server Gen No. Status Run ID Block No. Ex-Status
# Windows
1 cd /d "<Suite Install-dir>\bin"
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
1 ./hcmdsdbsrv -status
Display result
(*1) If the pdlog02 file exists, open the pdlog02 file instead of pdlog01 file.
Display result
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
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.
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.
How to set the environmental variable is different between Windows and Solaris. See (2-1) for
Windows, (2-2) for Solaris.
<Step1> Execute the following command for setting the environmental variable
# Command
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
# Command
1 set PDDIR
Display result
PDDIR=<Suite Install-dir>\HDB
<Step1> Execute the following command for setting the environmental variable
Depending on the type of shell, how to set the environmental variable differs.
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
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
4 Shell other than the above refer to the manual of each shell.
<Step2> Confirm that the environmental variable PDDIR is set by executing the following
command
# Command
Display result
PDDIR=/opt/HiCommand/Base/HDB
# Command
[Note] When the extended database log file is not used, KFPS01273-E reason code=1607-0"
and "KFPS01280-E1601-0" message is output, but please ignore it, this is no problem.
Display result
KFPS01273-E Unable to change log file status. element file:log7, system A/B:a, reason code=1607-0
Windows
<Suite Install-dir>\HDB\CONF
Solaris
/opt/HiCommand/Base/HDB/CONF
iv) Confirm that the message is output like Display result by executing the following
command.
# Command
1 pdconfchk
Display result
(a) Delete the database log file by executing the following command.
# Command
# Command
(5) Delete the file system to which the database log file is stored by executing the following
command.
# Command
Confirm that rdX1, rdX2, rdX3, rdX4, rdX5, rdX6 are successfully deleted under
<Extended directory>.
(6) Confirm that the database log file is deleted from the system by executing the following
command.
When the database log file is successfully deleted from the system, the log 7 log 12 is not output
by the command.
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 --------
# Windows
1 cd /d "<Suite Install-dir>\bin"
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
1 ./hcmdsdbsrv -status
Display result
(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
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.
.
12. HDvM Device Manager
13. Default %SystemDrive%\Program %SystemDrive%\Program
2 installation Files\HiCommand\TuningManager Files\CVXPAE\TuningManager
. directory for
Tuning
Manager
server (For
370 Hitachi Proprietary Information
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))
15. Default %SystemDrive%\Program %SystemDrive%\Program
installation Files\HiCommand\Base Files\CVXPAE\Base
directory for
Common
Component
(For Windows
Server 2003
(x86) and
Windows
Server 2008
(x86))
16. Default %SystemDrive%\Program Files %SystemDrive%\Program Files
installation (x86) \HiCommand\Base (x86) \CVXPAE\Base
directory for
Common
Component
(For Windows
Server 2003
(x64) and
Windows
Server 2008
(x64))
.
13. HDvM Device Manager
14. Default %SystemDrive%\Program %SystemDrive%\Program
2 installation Files\HiCommand\TuningManager Files\CVXPAE\TuningManager
. directory for
374 Hitachi Proprietary Information
Tuning
Manager
server (For
Windows
Server 2003
(x86) and
Windows
Server 2008
(x86))
15. 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))
16. Default %SystemDrive%\Program %SystemDrive%\Program
installation Files\HiCommand\Base Files\CVXPAE\Base
directory for
Common
Component
(For Windows
Server 2003
(x86) and
Windows
Server 2008
(x86))
17. Default %SystemDrive%\Program Files %SystemDrive%\Program Files
installation (x86) \HiCommand\Base (x86) \CVXPAE\Base
directory for
Common
Component
(For Windows
Server 2003
(x64) and
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.3 Terms
The following terms are used in this section.
# Terms Folder
-installation-directory <Installation-directory>\Base
1
[ In Ver.8 or later ]
<Installation-directory>\Base64
2 Hitachi-Tuning-Manager-installation-directory <Installation-directory>\TuningManager
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:
[ In Ver.8 or later ]
%SystemDrive%\Program Files\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.
Suite products
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
Start Agent
7-a.8(1)
Stop Agent
7-a.9(1)
7-a.11
Back up the performance data
for Tuning Manager API (Ver. 8.0 or later)
End
Figure 7-a.7-1 An overview of the procedure for backing up the Tuning Manager server and Agent databases
# Command line
cd <Hitachi-Tuning-Manager-installation-directory>\bin\
htm-db-status
Output example
KATN01314-I The command htm-db-status will now be executed.
Database Capacity (Used/Total): 15560 / 2048000 kBytes
Area Path:
D:\Program Files\HiCommand\TuningManager\database\TuningManager\TM00
KATN01309-I The database status has been displayed.
Output example
KAPM05320-I Backup successfully ended : CommonComponent Database.
Note: For details about the hcmdsbackups command, see the manual.
7-a.6 Back up the definition information files for the Tuning Manager server
Use the Windows COPY command to back up the definition information files for the
Tuning Manager server. For a list of the Tuning Manager server definition information
files to back up, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
The following shows an example of using the Windows COPY command to back up the
definition information files for the Tuning Manager server. For this example, the
destination folders used by the COPY command must be created in advance.
# Command line
COPY <Hitachi-Tuning-Manager-installation-installation-directory>\jp1pc\jpchosts
d:\backup\HiCommand\TuningManager\jp1pc
COPY<Hitachi-Tuning-Manager-installation-installation-directory>\jp1pc\*.ini
d:\backup\HiCommand\TuningManager\jp1pc
COPY <Hitachi-Tuning-Manager-installation-installation-directory>\jp1pc\bin\action\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\bin\action
COPY <Hitachi-Tuning-Manager-installation-installation-directory>\jp1pc\bin\statsvr\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\bin\statsvr
COPY <Hitachi-Tuning-Manager-installation-directory>\conf\user.properties
d:\backup\HiCommand\TuningManager\conf
COPY <Hitachi-Tuning-Manager-installation-directory>\conf\logging.properties
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\clator\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\clator
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.DB
d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.IDX
d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager\*.DAT
d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\store\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\store
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\store\*.DAT
d:\backup\HiCommand\TuningManager\jp1pc\mgr\store
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr\*.DB
d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr\*.IDX
d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\trapgen\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\trapgen
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr\viewsvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\data\*
d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr\data
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\reports\*
d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\agt0\agent\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\agt0\agent
COPY <Hitachi-Tuning-Manager-installation-directory>\jp1pc\agt0\store\*.ini
d:\backup\HiCommand\TuningManager\jp1pc\agt0\store
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\ui.properties
d:\backup\HiCommand\TuningManager\system\sysconf
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\core.properties
d:\backup\HiCommand\TuningManager\system\sysconf
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\cli.properties
d:\backup\HiCommand\TuningManager\system\sysconf
d:\backup\HiCommand\TuningManager\system\sysconf
COPY <Hitachi-Tuning-Manager-installation-directory>\system\sysconf\system.logging.properties
d:\backup\HiCommand\TuningManager\system\sysconf
The following shows an example of using the Windows COPY command to back up the
definition information files for Performance Reporter. For this example, the destination
folders used by the COPY command must be created in advance.
# Command line
COPY <Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\conf\*.*
d:\backup\HiCommand\TuningManager\PerformanceReporter\conf
Back up the Performance Reporter bookmarks stored in the following folder, by using
the Windows XCOPY command to copy the folder in its entirety.
# Folder
<Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\bookmarks
Note: The above folder is an example when the "bookmarkRepository" item of the
initialization settings file (config.xml) of Performance Reporter is not specified. Back up
Performance Reporter bookmarks from the folder specified as the
"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:
<Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\bookmarks
d:\backup\HiCommand\TuningManager\PerformanceReporter\bookmarks
7-a.7(ii) Back up the definition information files for Tuning Manager REST Application
Service (Ver. 8 or later)
In version 8.0.0 or later, if you are using Tuning Manager API, backup of definition
information files for Tuning Manager REST Application Service are required. Refer to
the following backup files.
2 system\ -
3 sysconf\ rest.properties
4 rest_raidinstance_info
5 rest_nasinstance_info
6 rest_host_info
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.
# Command line
1 cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
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.
The following shows an example of using the Windows COPY command to back up the
definition information files for Agent. For this example, the destination folders used by
the COPY command must be created in advance.
391 Hitachi Proprietary Information
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
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,
see 4.1.5. jpcras command.
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.1 Purpose
This section describes the procedure for restoring the Tuning Manager server data and the Agent
database on a host on which these products are installed in a Windows environment.
7-b.2 Prerequisites
See the description of restoration in the following manual and confirm that the described
preconditions are satisfied. If you perform restoration when not all the preconditions are satisfied,
you will be unable to restore data normally.
[ manual title]
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
Hitachi Command Suite Tuning Manager Agent Administration Guide
7-b.4 Terms
The following terms are used in this section.
# Terms Folder
Hitachi-StorageCommand-Suite-Common-Component <Installation-directory>\Base
1
-installation-directory
2 Hitachi-Tuning-Manager-installation-directory <Installation-directory>\TuningManager
Installation-directory for Windows Server 2003 x86, and Windows Server 2008 x86:
%SystemDrive%\Program Files\HiCommand
3 for Windows Server 2003 x64, Windows Server 2008 x64 and Windows
Server 2012:
4 Agent-installation-directory <Installation-directory>\TuningManager\jp1pc
Note: Unless you specify other directories during installation, the above directories are used by
default.
Restore the definition information files for the Tuning Manager 7-b.7
End
Figure 7-b.7-1 An overview of the procedure for restoring the Tuning Manager server and Agent databases
# Command line
1 cd <Hitachi-Tuning-Manager-installation-directory>\bin\
[ In Ver.8 or later ]
Output example
KAPM06903-I The service was stopped successfully.
Note: For details about the hcmdsdb command, see the manual.
7-b.7 Restore the definition information files for the Tuning Manager server
Use the Windows COPY command to copy the backed-up Tuning Manager server definition
information files, overwriting the files at the destination. For a list of the Tuning Manager server
definition information files to restore, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
The following shows an example of using the Windows COPY command to restore the definition
information files for the Tuning Manager server:
# Command line
1 COPY d:\backup\HiCommand\TuningManager\jp1pc\jpchosts
2 COPY d:\backup\HiCommand\TuningManager\jp1pc\*.ini
4 COPY d:\backup\HiCommand\TuningManager\jp1pc\bin\statsvr\*.ini
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
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager
10 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.IDX
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager
11 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\manager\*.DAT
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\manager
12 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\store\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\store
13 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\store\*.DAT
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\store
14 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr
15 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr\*.DB
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr
16 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\namesvr\*.IDX
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\namesvr
17 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\trapgen\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\trapgen
18 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr
19 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvrdata\*
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\data
20 COPY d:\backup\HiCommand\TuningManager\jp1pc\mgr\viewsvr\reports\*
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\mgr\viewsvr\reports
21 COPY d:\backup\HiCommand\TuningManager\jp1pc\agt0\agent\*.ini
<Hitachi-Tuning-Manager-installation-directory>\jp1pc\agt0\agent
22 COPY d:\backup\HiCommand\TuningManager\jp1pc\agt0\store\*.ini
23 COPY d:\backup\HiCommand\TuningManager\system\sysconf\ui.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
24 COPY d:\backup\HiCommand\TuningManager\system\sysconf\core.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
25 COPY d:\backup\HiCommand\TuningManager\system\sysconf\cli.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
26 COPY d:\backup\HiCommand\TuningManager\system\sysconf\common.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
27 COPY d:\backup\HiCommand\TuningManager\system\sysconf\system.logging.properties
<Hitachi-Tuning-Manager-installation-directory>\system\sysconf
The following shows an example of using the Windows COPY command to restore the definition
information files for Performance Reporter:
# Command line
1 COPY d:\backup\HiCommand\TuningManager\PerformanceReporter\conf\*.*
<Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\conf
Copy the backup of the bookmarks folder for Performance Reporter to the following folder,
overwriting the files at the destination.
# 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.
# Command line
1 XCOPY /e /y /I d:\backup\HiCommand\TuningManager\PerformanceReporter\bookmarks
<Hitachi-Tuning-Manager-installation-directory>\PerformanceReporter\bookmarks
7-b.8(ii) Restore the definition information files for Tuning Manager REST Service
(Ver. 8.0 or later)
In version 8.0, if you are using Tuning Manager API, it is necessary to restore the
definition information files for Tuning Manager REST Application Service.
Copy the backed up files (see 7.a.7(ii)) matching the directory structure of the
destination (for restoring).
# Command line
1 cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
2 jpcstop all
# Command line
1 cd <Hitachi-Tuning-Manager-installation-directory>\jp1pc\tools
2 jpcresto agtd d:\backup\DS1RAID[host01]
Output example
Note: For details about the jpcresto command, see the manual.
The following shows an example of how to use the Windows "COPY" command to restore the Agent
definition information files.
Note that files #5 and #6 might not exist in certain environments. If these files do not exist, the
"COPY" command will fail. However, the failure of this command does not affect the backup
operation.
# Command line
1 COPY d:\backup\HiCommand\TuningManager\jp1pc\xxxx\agent\*.ini
<Agent-installation-directory>\xxxx\agent
2 COPY d:\backup\HiCommand\TuningManager\jp1pc\xxxx\agent\instance-name\*.ini
<Agent-installation-directory>\xxxx\agent\instance-name
3 COPY d:\backup\HiCommand\TuningManager\jp1pc\xxxx\store\*.ini
<Agent-installation-directory>\xxxx\store
4 COPY d:\backup\HiCommand\TuningManager\jp1pc\xxxx\store\instance-name\*.ini
<Agent-installation-directory>\xxxx\store\instance-name
5 COPY d:\backup\HiCommand\TuningManager\jp1pc\agtw\agent\agtw.properties
<Agent-installation-directory>\agtw\agent
6 COPY d:\backup\HiCommand\TuningManager\jp1pc\agtt\agent\jpcapp
<Agent-installation-directory>\agtt\agent
7-b.11 Restore the definition information files for HTnM-Agent REST Services (Ver. 8.0 or
later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must restore the definition information files for HTnM-Agent REST Services. Copy the backed
up files (see 7.a.10) matching the directory structure of the destination (for restoring).
7-b.12 Restore the performance data for Tuning Manager API (Ver. 8.0 or later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must restore the performance data for Tuning Manager API. Copy the backed up performance
data (see 7.a.11) matching the directory structure of the destination (for restoring).
[Note]
By editing the property file (apidataglobalconfig.ini or jpcagt.ini) the output destination of the
performance data can be changed. If the output destination for performance data has been changed,
copy the backed up files to the changed output destination of the performance data.
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.3 Terms
The following terms are used in this section.
# Terms Directory
/opt/HiCommand/Base
1
[ In Ver.8 or later ]
/opt/HiCommand/Base64
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
Note: Unless you specify other directories during installation, the above directories are used by
default.
Start
Described in 7-c.5 Back up data for Hitachi Storage Command
Suite products
7-c.5(2)
Execute the hcmdsbackups command
Back up the definition information files for the Tuning Manager server
7-c.6
End
Figure 7-c.7-1 An overview of the procedure for backing up the Tuning Manager server and Agent databases
# Command line
1 For Solaris:
cd /opt/HiCommand/TuningManager/bin
For Linux :
cd <TuningManager-Installation-directory>/bin
2 ./htm-db-status
Output example
KATN01314-I The command htm-db-status will now be executed.
Database Capacity (Used/Total): 15560 / 2048000 kBytes
Area Path:
/TMP/Program Files/HiCommand/TuningManager/database/TuningManager/TM00
KATN01309-I The database status has been displayed.
# Command line
1 For Solaris :
cd /opt/HiCommand/Base/bin
For Linux :
cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
2 [ In Ver.6 to earlier than 8 ]
./hcmdsbackups -dir /tmp/backup/hcmdsbackups -auto
[ In Ver.8 or later ]
./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
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
The following shows an example of using the UNIX cp command to back up the definition
information files for the Tuning Manager server. For this example, the destination folders used by
the cp command must be created in advance.
# Command line
1 cp /opt/jp1pc/jpchosts /tmp/backup/opt/jp1pc
2 cp /opt/jp1pc/*.ini /tmp/backup/opt/jp1pc
3 cp /opt/jp1pc/bin/action/*.ini /tmp/backup/opt/jp1pc/bin/action
4 cp /opt/jp1pc/bin/statsvr/*.ini /tmp/backup/opt/jp1pc/bin/statsvr
5 cp /opt/<TuningManager-Installation-directory>/conf/user.properties
/tmp/backup/<TuningManager-Installation-directory>/conf
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
# Command line
1 cd /opt/jp1pc/tools
2 ./jpcstart all
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.
2 mkdir /tmp/backup/DS1RAID[host01]
Note: For details about the jpcctrl backup command, see the manual.
# Command line
1 cd /opt/jp1pc/tools
2 ./jpcstop all
The following shows an example of using the Unix cp command to back up the definition
information files for Agent. For this example, the destination folders used by the cp command
must be created in advance.
Note that file #8 might not exist in certain environments. If this file does not exist, the "cp"
command will fail. However, the failure of this command does not affect the backup operation.
# Command line
1 cp /opt/jp1pc/xxxx/agent/*.ini /tmp/backup/opt/jp1pc/xxxx/agent
2 cp /opt/jp1pc/xxxx/agent/instance-name/*.ini /tmp/backup/opt/jp1pc/xxxx/agent/instance-name
3 cp /opt/jp1pc/xxxx/store/*.ini /tmp/backup/opt/jp1pc/xxxx/store
4 cp /opt/jp1pc/xxxx/store/instance-name/*.ini /tmp/backup/opt/jp1pc/xxxx/store/instance-name
5 cp /opt/jp1pc/agtu/agent/jpcapp /tmp/backup/opt/jp1pc/agtu/agent
6 cp /opt/jp1pc/agtu/agent/evfile /tmp/backup/opt/jp1pc/agtu/agent
7 cp /opt/jp1pc/agtu/agent/wgfile /tmp/backup/opt/jp1pc/agtu/agent
8 cp /opt/jp1pc/agtt/agent/jpcapp /tmp/backup/opt/jp1pc/agtt/agent
7-c.10 Back up the definition information files for HTnM-Agent REST Services (Ver.8.0 or
later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must back up the definition information file for HTnM-Agent REST Services. Back up
procedure is the same as (7-a.10). When using copy command of OS for copying, execute
the copy command corresponding to each platform.
7-c.11 Back up the performance data for Tuning Manager API (Ver.8.0 or later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must back up the performance data for Tuning Manager API. Back up procedure is the same
as (7-a.11). When using copy command of OS for copying, execute the copy command
corresponding to each platform.
The following table lists execution examples of the htmhsbackup command in a UNIX
environment.
# Command Line
1 cd /opt/jp1pc/htnm/bin
2 mkdir /tmp/RAID_backup
3 ./htmhsbackup -dir /tmp/RAID_backup
7-d.1 Purpose
This section describes the procedure for restoring the Tuning Manager server data and the Agent
database on a host on which these products are installed in a UNIX environment.
7-d.2 Prerequisites
See the description of restoration in the following manual, and confirm that the described
preconditions are satisfied. If you perform restoration when not all the preconditions are satisfied,
you will be unable to restore data normally.
[manual title]
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
Hitachi Command Suite Tuning Manager Agent Administration Guide
7-d.4 Terms
The following terms are used in this section.
# Terms Directory
/opt/HiCommand/Base
1
[ In Ver.8 or later ]
/opt/HiCommand/Base64
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
Restore the definition information files for the Tuning Manager 7-d.7
7-d.8
Restore the definition information files for Performance Reporter
Stop Agent
7-d.9(1)
7-d.12
Restore the performance data
for Tuning Manager API (Ver. 8.0 or later)
End
Figure 7-d.7-1 An overview of the procedure for restoring the Tuning Manager server and Agent databases
# Command line
1 For Solaris :
cd /opt/HiCommand/Base/bin
For Linux :
cd <Hitachi-Command-Suite-Common-Component-Installation-directory>/bin
[ In Ver.8 or later ]
Output example
KAPM06903-I The service was stopped successfully.
Note: For details about the hcmdsdb command, see the manual.
7-d.7 Restore the definition information files for the Tuning Manager server
Use the UNIX cp command to copy the backed-up Tuning Manager server definition information
files, overwriting the files at the destination. For a list of the Tuning Manager server definition
information files to restore, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
The following shows an example of using the UNIX cp command to restore the definition
information files for the Tuning Manager server:
# Command line
1 cp /tmp/backup/opt/jp1pc/jpchosts /opt/jp1pc
2 cp /tmp/backup/opt/jp1pc/*.ini /opt/jp1pc
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
<TuningManager-Installation-directory>/system/sysconf
25 cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/cli.properties
<TuningManager-Installation-directory>/system/sysconf
26 cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/common.properties
<TuningManager-Installation-directory>/system/sysconf
27 cp /tmp/backup<TuningManager-Installation-directory>/system/sysconf/system.logging.properties
<TuningManager-Installation-directory>/system/sysconf
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 :
<TuningManager-Installation-directory>/PerformanceReporter
7-d.8(ii) Restore the definition information files for Tuning Manager REST Service
(Ver. 8.0 or later)
In version 8.0, if you are using Tuning Manager API, it is necessary to restore the
definition information files for Tuning Manager REST Application Service. Restore
procedure is the same as (7-b.8(ii)). When using copy command of OS for copying,
execute the copy command corresponding to each platform.
# Command line
1 cd /opt/jp1pc/tools
2 ./jpcstop all
Output example
Note: For details about the jpcresto command, see the manual.
The following shows an example of using the Unix cp command to restore the definition
information files for Agent:
# Command line
1 cp /tmp/backup/opt/jp1pc/xxxx/agent/*.ini /opt/jp1pc/xxxx/agent
2 cp /tmp/backup/opt/jp1pc/xxxx/agent/instance-name/*.ini /opt/jp1pc/xxxx/agent/instance-name
3 cp /tmp/backup/opt/jp1pc/xxxx/store/*.ini /opt/jp1pc/xxxx/store
4 cp /tmp/backup/opt/jp1pc/xxxx/store/instance-name/*.ini /opt/jp1pc/xxxx/store/instance-name
5 cp /tmp/backup/opt/jp1pc/agtu/agent/jpcapp /opt/jp1pc/agtu/agent
6 cp /tmp/backup/opt/jp1pc/agtu/agent/evfile /opt/jp1pc/agtu/agent
7 cp /tmp/backup/opt/jp1pc/agtu/agent/wgfile /opt/jp1pc/agtu/agent
8 cp /tmp/backup/opt/jp1pc/agtw/agent/agtw.properties /opt/jp1pc/agtw/agent
Note: xxxx indicates the service key of each Agent. For details on the service keys of each Agent,
see 4.1.5. jpcras command.
7-d.11 Restore the definition information files for HTnM-Agent REST Services
(Ver. 8.0 or later)
In version.8 or later, if Agent operates with Store database and the Tuning Manager API is enabled,
you must restore the definition information file for HTnM-Agent REST Services. Restore
procedure is the same as (7-b.11). When using copy command of OS for copying, execute
the copy command corresponding to each platform.
In Ver.7 or later, when reading, replace the terms in the text according to the following table.
The permission of file and directory that is placed or generated below /opt/jp1pc follows the
Agent policy.
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
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)
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.
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
[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.
- 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]
10-d.2 Causes
The HCS service is forcibly terminated when establishing a cluster environment because the
cluster software is attempting to start or stop the HCS service set in the standby system under
the following condition:
- HDvM and HTnM are installed on the executing node, but only HDvM is installed on the
standby node (HTnM is not installed on the standby node).
Under the above condition, if the HTnM is installed on the standby node, the parameter related
to HiRDB memory (pd_max_users) is changed (the message shown above is issued),
leading to a difference between the parameters of the executing node and the standby node.
This causes the HiRDB service to become unable to start.
10-d.3 Solutions
To recover HiRDB:
(1) Take the HCS service offline from the cluster software.
(7) Change the HiRDB setting changed in (3) back to its original value.
Change line 13 of the following file as shown below:
<Common-Component-installation-directory>\HDB\CONF\pdsys
from set pd_max_users = 84
to set pd_max_users = 96
(8) Change HiRDB to the online status from the cluster software.
(9) Confirm whether HiRDB is online (the status has recovered) from the cluster software.
- KAVE05033-E Message
[Message]
KAVE05033-E A service could not start. (service=Agent for UNIX,
rc=-5)
[Log output destination]
jpclog
10-e.2 Causes
An error like above is caused by the difference in the number of bits between AIX (64-bit) and
Agent for Platform (32-bit). Such a difference in the number of bits seems to result from a
change in the number of bits between the 32-bit and 64-bit versions of AIX.
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.
-Output example
[ In Ver.8 or later ]
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
tzupdater version 1.3.62-b01 ------ tzupdater tool version
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
tzupdater version 1.3.62-b01 ------ tzupdater tool version
JRE time zone data version: tzdata2013d ------ Current tzdata version
Embedded time zone data version: tzdata2013i ------ Updated tzdata version
-Output example
[ In Ver.6 to earlier than 8 ]
For Windows
"C:\Program Files\HiCommand\Base\jdk\bin\java" -Djava.vendor="Sun Microsystems Inc." -jar
"C:\Program Files\HiCommand\Base\tzupdater.jar" -v -u
java.home: C:\Program Files\HiCommand\Base\jdk\jre ------JDK to be applied
java.vendor: Sun Microsystems Inc. ------Vendor name specified in the command line
java.version: 1.5.0_11 ------JDK version
JRE time zone data version: tzdata2007g ------ Current tzdata version
Embedded time zone data version: tzdata2010f ------ Updated tzdata 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
java.vendor: Sun Microsystems Inc. ------Vendor name specified in the command line
java.version: 1.5.0_05 ------JDK version
JRE time zone data version: tzdata2007g ------ Current tzdata version
Embedded time zone data version: tzdata2010f ------ Updated tzdata version
Extracting files... done.
Renaming directories... done.
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.
[ In Ver.8 or later ]
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
java.vendor: Sun Microsystems Inc. ------Vendor name specified in the command line
java.version: 1.5.0_11 ------JDK version
JRE time zone data version: tzdata2013d ------ Current tzdata version
Embedded time zone data version: tzdata2013i ------ Updated tzdata version
Extracting files... done.
Renaming directories... done.
Validating the new time zone data... done.
Time zone data update is complete.
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
java.vendor: Sun Microsystems Inc. ------Vendor name specified in the command line
java.version: 1.5.0_05 ------JDK version
JRE time zone data version: tzdata2013d ------ Current tzdata version
Embedded time zone data version: tzdata2013i ------ Updated tzdata version
Extracting files... done.
Renaming directories... done.
Validating the new time zone data... done.
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.
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:
Stop unnecessary applications and close windows to increase the available memory, and then retry.
12-a.2 Causes
Cause of case 1:
The cause of case 1 is that many records are to be output, but there is not enough memory in
View Server to output a report. In the message shown in Case 1, "ViewServer error code:
-2001" indicates that View Server memory is insufficient. For details, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Agent Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Agent Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Agent Administration Guide
Cause of case 2:
The cause of case 2 is that many records are to be output, but there is not enough memory in PR
to output a report. You can also execute the jpcrpt command to display the log
jpcrpt_logX.log, where you can check whether memory is insufficient in PR.
become insufficient. A server memory shortage occurred. Stop unnecessary applications and close windows to
12-a.3 Solutions
(1) Enable split transmission mode for a CSV-format report
When a report is output by executing the jpcrpt command with split transmission mode
enabled, PR can receive split report data from View Server. This might prevent a memory heap
shortage in View Server or PR, but it cannot be used for output of an HTML report.
To set split transmission mode, set blockTransferMode in the PR initialization settings file
(config.xml) to true. For details, see the following manual:
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
(3) Increasing the Java heap size used by the jpcrpt command
You can specify the maximum Java heap size that the jpcrpt command can use with the mx
If the problem cannot be avoided by performing (1),(2) and (3) above when you use the HTML
format, consider outputting the data to a CSV file. Also consider changing the report definition so
that the number of records output at one time is restricted based on a period or metric.
12-b Actions to be taken when Main Console terminates abnormally during polling
12-b.1 Cases
When an attempt is made to log in to HTnM, the message HTTP 500 Internal server
Error appears in the browser, and login is impossible.
12-b.2 Causes
The cause of this problem is that Main Console terminates abnormally because the memory
heap in Main Console was insufficient during polling. If you check the javalog for Main
Console, you will see that a Java memory shortage has occurred.
[ In Ver.6 to earlier than 8 ]
[HCS-installation-directory\Base\CC\web\containers\TuningManager\logs\javalogXX.log]
[ In Ver.8 or later ]
[HCS-installation-directory\Base64\CC\web\containers\TuningManager\logs\javalogXX.log]
174783K->174783K(174784K)][DefNew::Survivor: 20018K->19993K(21824K)][Tenured:
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.
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.
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.
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
*1: The output information differs depending on the destination to which the instance is connected. For details on the
5 Cisco(Seed Switch)
connected
Table14.a.1-1 Service IDs and service keys specified when performing backup and restore
operations
# Product Service ID Service key
(*) See the section Changing a host name after starting operations in the following manual:
- In Ver.6
Hitachi Tuning Manager Software Installation Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Installation Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Installation Guide
15-b Action to take if you cannot restore the old host name
This section describes the action to be taken only if you cannot restore the old host name.
The action differs depending on the host:
(1) If the name of an HTnM server host was changed, see 15-b.1.
(2) If the name of an HTnM agent host was changed, see 15-b.2.
15-b.1 Action to take if the name of an HTnM server host was changed
(1) Change the Common Component settings as described in the section Changing the settings of
the Hitachi Command Suite Common Component database of the following manual:
- In Ver.6
Hitachi Tuning Manager Software Server Administration Guide
- In Ver.7
Hitachi Command Suite Tuning Manager Software Server Administration Guide
- In Ver.8
Hitachi Command Suite Tuning Manager Server Administration Guide
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.
(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.
(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.
If the jpcctrl list "*" command results include service information with service IDs that
include the old host name in the Service ID column and with the changed host name in
Host Name, specify the host names and execute the command as follows:
jpcctrl delete "???< the old host name >" host=< the changed host name >
jpcctrl delete "*[< the old host name >]" host=< the changed host name >
If the KAVE05233-W message is output and the service information fails to delete when
the command is executed, specify the force option and execute the command again.
3. Execute the jpcctrl list command to confirm that the service information was correctly
deleted.
jpcctrl list "*" host=< the old host name >
jpcctrl list "*" host=< the changed host name >
Check the output of the above two commands to confirm that no entries have the old host
name in the Service ID column.
(13) Change the settings of the connection-target HTnM server on the HTnM agents host.
On the HTnM agents host connected to the HTnM server, change the settings of the
connection-target HTnM server. Use the jpcnshostname command to change the
connection-target HTnM server settings. For example, to change the host name of the
connection-target HTnM server to "hostB", specify the host name and execute the command as
shown below.
If the HTnM agents connected to the HTnM server is operating in a logical host environment,
you must use the -lhost option to specify the logical host name of the HTnM agents host.
jpcnshostname -s hostB
or
jpcnshostname -s hostB -lhost < the logical host name of HTnM agents >
(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
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
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.
(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.
(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.
If the jpcctrl list "*" command results include service information with service IDs that
include the old host name in the Service ID column and with the changed host name in
Host Name, specify the host names and execute the command as follows:
jpcctrl delete "???< the old host name >" host=< the changed host name >
jpcctrl delete "*[< the old host name >]" host=< the changed host name >
or
jpcctrl delete "???< the old host name >" host=< the changed host name >
lhost=< the logical host name of the HTnM server host >
jpcctrl delete "*[< the old host name >]" host=< the changed host name > lhost=< the
logical host name of the HTnM server host >
If the KAVE05233-W message is output and the service information fails to delete when
the command is executed, specify the force option and execute the command again.
3. Execute the jpcctrl list command to confirm that the service information was correctly
deleted.
jpcctrl list "*" host=< the old host name >
jpcctrl list "*" host=< the changed host name >
or
jpcctrl list "*" host=< the old host name > lhost=< the logical host name of the HTnM
server host >
jpcctrl list "*" host=< the changed host name > lhost=< the logical host name of the HTnM
server host >
Check the output of the above two commands to confirm that no entries have the old host
name in the Service ID column.
0 or 1
No
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.
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.
3 Hybrid Store Hybrid Store NAS Agent Hybrid Store StoreDB P Procedure B
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
For Windows:
For UNIX:
/opt/jp1pc/htnm/agent/system/data_file_manage.ini
- Modification
<Before modification>
[Mode]
Database Type=ScalableDB
<After modification>
[Mode]
Database Type=Store
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
<Before modification>
add.jvm.arg=-Xmx6144m
<After modification>
add.jvm.arg=-Xmx1024m
For Windows:
<installation-folder>\agtX\ migration_status.ini
For UNIX:
/opt/jp1pc/agtX/migration_status.ini
<installation-folder>\agtX\support_switch_db.ini
For UNIX:
/opt/jp1pc/agtX/support_switch_db.ini
For Windows:
<installation-folder>\agtX\agent\dbmigrating.dat
For UNIX:
/opt/jp1pc/agtX/agent/dbmigrating.dat
(8) Specify the output destination of the operating performance information file for RAID Agent.
Follow this step if you are using Tuning Manager API on RAID Agent, and you want to
change the output destination of the operating performance information file. If you want to
Change the output destination, see the Hitachi Command Suite Tuning Manager Agent
Administration Guide.
Procedure B:
If RAID Agent and NAS Agent both use Hybrid Store, and you want to change the data storage
format to Store DB independently for NAS Agent, follow the steps below:
(1) Execute the following htmsrv command on Agent host to stop all services:
htmsrv stop -all
For Windows:
<installation-folder>\agtX\ migration_status.ini
For UNIX:
/opt/jp1pc/agtX/migration_status.ini
For Windows:
<installation-folder>\agtX\support_switch_db.ini
For UNIX:
/opt/jp1pc/agtX/support_switch_db.ini
For Windows:
<installation-folder>\agtX\agent\dbmigrating.dat
For UNIX:
/opt/jp1pc/agtX/agent/dbmigrating.dat
Procedure C:
If only NAS Agent is installed, follow the steps below:
(1) Execute the following htmsrv command on Agent host to stop all services:
htmsrv stop -all
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
For Windows:
<installation-folder>\agtX\ migration_status.ini
For UNIX:
/opt/jp1pc/agtX/migration_status.ini
For Windows:
<installation-folder>\agtX\support_switch_db.ini
For UNIX:
/opt/jp1pc/agtX/support_switch_db.ini
<installation-folder>\agtX\agent\dbmigrating.dat
For UNIX:
/opt/jp1pc/agtX/agent/dbmigrating.dat
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
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
-End of document-