7.4.1 In Windows
- Organization of this subsection
(1) OS log information
The table below shows the types of OS log information that need to be collected.
|
Information type |
Overview |
Default file name |
Collectable using the jpcras command? |
|---|---|---|---|
|
System log |
Windows event log |
N/A |
Y |
|
WMI log |
system-folder\system32\WBEM\Logs\* # |
Y |
|
|
Process information |
Process list |
N/A |
Y |
|
System file |
hosts file |
system-folder\system32\drivers\etc\hosts |
Y |
|
services file |
system-folder\system32\drivers\etc\services |
Y |
|
|
OS information |
System information |
N/A |
Y |
|
Network status |
N/A |
Y |
|
|
Host name |
N/A |
Y |
|
|
Windows Firewall information |
N/A |
Y |
|
|
Dump information |
Log file for problem reports and solutions |
user-mode-process-dump-output-folder\program-name.process-ID.dmp
|
N |
- Legend:
-
Y: Can be collected
N: Cannot be collected
N/A: Not applicable
- #
-
If log files are set to be output to a different folder, collect data from the applicable folder.
(2) Performance Management information
The following types of information related to Performance Management need to be collected. If a problem occurred with a network connection, you also need to collect files from the target machine. The table below shows the Performance Management information.
|
Information type |
Overview |
Default file name |
Collectable using the jpcras command? |
|---|---|---|---|
|
Common message log |
Message log output by Performance Management (Sequential file method) |
installation-folder\log\jpclog{01|02}#1 |
Y |
|
Message log output by Performance Management (Wrap-around file method) |
installation-folder\log\jpclogw{01|02}#1 |
Y |
|
|
Configuration information |
Each configuration information file |
N/A |
Y |
|
jpctool service list (jpcctrl list) command output result |
N/A |
Y |
|
|
Version information |
Product version |
N/A |
Y |
|
History information |
N/A |
Y |
|
|
Database information |
Remote Monitor Store service |
*.DB and *.IDX files in the following folders: installation-folder\agt8\store\instance-name\STPD installation-folder\agt8\store\instance-name\STPI |
Y |
|
Trace log |
Trace information of each Performance Management program service |
N/A#2 |
Y |
|
Collected log |
Information when performance information was collected |
installation-folder\agt8\agent\instance-name\log\VM_Type_monitoring-target-name*.log installation-folder\agt8\agent\instance-name\targets\monitoring-target-name\log\jpcagt5virtage*.log |
Y |
|
Work data |
Work data when performance information was collected |
installation-folder\agt8\agent\instance-name\targets\monitoring-target-name\work\* installation-folder\agt8\agent\instance-name\targets\monitoring-target-name\data\* |
Y |
|
Collector plug-in data |
Data for each collector plug-in |
installation-folder\agt8\plugin\jpcagt5*.d\* installation-folder\agt8\plugin\jpcagt8*.d\* |
Y |
|
Installation log#3 |
Message log during installation |
system-folder\TEMP\HCDINST\*.LOG |
N |
- Legend:
-
Y: Can be collected
N: Cannot be collected
N/A: Not applicable
- #1
-
For the log file output method, see the chapter that explains error detection in the JP1/Performance Management User's Guide.
- #2
-
For the trace log storage folder, see 7.3.2(2) Trace log.
- #3
-
Collect this information if installation fails.
(3) Registry information
Collect registry information related to HNTRLib2. The table below shows the information to collect.
|
Information type |
Overview |
Registry key name |
Collectable using the jpcras command? |
|---|---|---|---|
|
Configuration information |
Each type of configuration information |
HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\HNTRLIB2\HNTR1 (other than the x64 environment) HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\HITACHI\HNTRLIB2\HNTR1 (in the x64 environment) |
Y |
- Legend:
-
Y: Can be collected
(4) Collector plug-in information of Hitachi Compute Blade logical partitioning feature (logical partitioning feature only)
When the virtual environment to be monitored is one with logical partitioning feature, the information listed in the table below is required.
|
Overview |
File name |
Collectable using the jpcras command? |
|---|---|---|
|
Temporary file for the LPAR Manager management command |
installation-folder\agt8\agent\instance-name\targets\monitoring-targetname\log\HvmPerMon.bin |
Y |
|
Definition file for the LPAR Manager management command (master file) |
installation-folder\agt8\plugin\jpcagt5virtage.d\jpcagt5virtageSetup.ini |
Y |
|
LPAR Manager management command |
installation-folder\agt8\plugin\jpcagt5virtage.d\HvmSh.exe |
Y |
|
Definition file for the LPAR Manager management command (copy of the file) |
installation-folder\agt8\agent\instance-name\targets\monitoring-targetname\jpcagt5virtageSetup.ini |
Y |
- Legend:
-
Y: Can be collected
(5) LPAR Manager dump information (logical partitioning feature only)
If an error occurs during a connection to Hitachi Compute Blade logical partitioning feature, or there is a problem with performance data obtained from the environment with Hitachi Compute Blade logical partitioning feature, capture the LPAR Manager dump. For details about how to capture an LPAR Manager dump, see the topic that describes the LPAR Manager dump capture command in the User's Guide for each Hitachi Compute Blade device.
(6) Operation content
You need the following types of information about the operation that was taking place when the problem occurred:
-
Detailed operation content
-
Time at which the problem occurred
-
Machine configuration (including the version of each OS, host name, and configuration of PFM - Manager and PFM - RM for Virtual Machine)
-
Whether the problem is reproducible
-
If the user logged on from PFM - Web Console, the Performance Management user name used for the logon
(7) Error information on the screen
Collect hard copies of the following:
-
Operation window if an application error occurred
-
Error message dialog box (including the description displayed when the Details button is clicked, if available)
-
The Command Prompt window if the problem occurred during command execution
(8) User-mode process dump
If a Performance Management process stops due to an application error, obtain a user-mode process dump.
(9) Collecting problem reports
If a Performance Management process stops due to an application error, obtain a problem report.
(10) Other information
In addition to the information described above, the following types of information are needed:
-
Argument specified for a command if the problem occurred during command execution