Job Management Partner 1/Performance Management - Agent Option for Virtual Machine Description, User's Guide and Reference
- Organization of this subsection
- (1) OS log information
- (2) Performance Management information
- (3) Registry information
- (4) Operation content
- (5) Error information on the screen
- (6) User dump (in Windows Server 2008)
- (7) Collecting problem reports (in Windows Server 2008)
- (8) Other information
(1) OS log information
The table below shows the types of OS log information that need to be collected.
Table 7-7 OS log information
Information type Overview Default file name Collectable using the jpcras command? System log Windows event log N/A 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 Dump information Dr. Watson file#1 system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log#2
system-drive\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dump#2Y
- Legend:
- Y: Can be collected
- N/A: Not applicable
- #1
- In Windows Server 2008, Dr. Watson has been replaced by Problem Reports and Solutions.
- #2
- 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.
Table 7-8 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 Agent Store service
- Store Version 1.0
installation-folder\agt5\store\instance-name\*.DB
installation-folder\agt5\store\instance-name\*.IDX
- Store Version 2.0
installation-folder\agt5\store\instance-name\STPD
The following files under the installation-folder\agt5\store\instance-name\STPI folder:
*.DB
*.IDX
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\agt5\agent\instance-name\log\jpcagt5vmwaren.log#3
installation-folder\agt5\agent\instance-name\log\jpcagt5hypervn.log#3Y Work data Work data when performance information was collected installation-folder\agt5\agent\instance-name\work\* Y Collector plug-in data Data for each collector plug-in installation-folder\agt5\plugin\jpcagt5*.d\* Y Installation log#4 Message log during installation
(in Windows Server 2003)%TEMP%\pfm_inst.log
The following files under the system-folder\Windows\TEMP\HCDINST folder:
- HCDMAIN.LOG and HCDMAINn.LOG#3
- HCDINST.LOG and HCDINSTn.LOG#3
- product-name.LOG
N Message log during installation
(in Windows Server 2008)%WINDOWS%\TEMP\HCDINST\product-model-name.LOG
The following files under the system-folder\Windows\TEMP\HCDINST folder:
- HCDMAIN.LOG and HCDMAINn.LOG#3
- HCDINST.LOG and HCDINSTn.LOG#3
- product-name.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 Job Management Partner 1/Performance Management User's Guide.
- #2
- For the trace log storage folder, see 7.3.2(2) Trace log.
- #3
- n indicates a number.
- #4
- Collect this log if installation fails. %TEMP% indicates the folder that is set in TEMP when the set command is executed from the command prompt.
(3) Registry information
Collect registry information related to HNTRLib2. The table below shows the information to collect.
Table 7-9 HNTRLib2 information (in Windows)
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) 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 - Agent)
- Whether the problem is reproducible
- If the user logged on from PFM - Web Console, the Performance Management user name used for the logon
(5) 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
(6) User dump (in Windows Server 2008)
In Windows Server 2008, if a Performance Management process stops due to an application error, obtain a user dump.
(7) Collecting problem reports (in Windows Server 2008)
In Windows Server 2008, if a Performance Management process stops due to an application error, obtain a problem report.
(8) Other information
In addition to the information described above, the following types of information are needed:
- Contents displayed for the System and Application items in Windows Event Viewer
- Contents displayed for System Information under System Tools in Accessories
- Argument specified for a command if the problem occurred during command execution
All Rights Reserved. Copyright (C) 2009, 2010, Hitachi, Ltd.