11.4.2 In UNIX
- Organization of this subsection
(1) Checking the process status
The process names that are displayed when the ps command is executed are shown below. In UNIX, by using the data collection tool (jim_log.sh), you can collect the execution results of the ps command along with other data.
(a) JP1/IM - Manager
For details about JP1/IM - Manager processes, see Appendix B.2 (1) JP1/IM - Manager in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.
(2) Outputting a dump file for JP1/IM
(a) JP1/IM - Manager
You only need to output a dump file for JP1/IM - Manager when the health check function detects an abnormality in JP1/IM - Manager. Execute the jcogencore command as follows.
jcogencore
When you execute the jcogencore command, a message appears asking you to select the process from which to output a dump file. Select the process that is included in the message information issued by the health check function. If a dump file already exists, an overwrite confirmation message is displayed. If you choose not to overwrite the dump file, choose n and terminate the command. Next, save the dump file and then re-execute the jcogencore command.
For details about the jcogencore command, see jcogencore (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
(3) Executing the data collection tool
This subsection describes execution of the data collection tool (jim_log.sh).
When you execute the jim_log.sh command, which is provided by JP1/IM - Manager, you can collect the data necessary for troubleshooting JP1/IM - Manager and JP1/Base on the same host.
Because the total volume of data collected by a data collection tool is massive, you need to estimate it before you execute the command and make sure the machine you are using has sufficient free space. For the volume of data that will be collected by the jim_log.bat command, see the JP1/IM - Manager release notes.
A tool execution example follows.
# /opt/jp1imm/tools/jim_log.sh -f data-storage-directory
When you execute the tool, the collected data is summarized in the tar format and output as compressed data.
(4) Checking the operation content
Check the content of the operation that was taking place when the problem occurred, and record it. The following types of information must be checked:
-
Operation content details
-
Time of problem occurrence
-
Reproducibility
-
Login user name that was used to log in from JP1/IM - View
-
Machine configuration (version of each OS, host name, and Central Console configuration)
(5) Collecting the error information on the screen
If an error is displayed on the screen, collect that information as well. Collect a hard copy of the following:
-
Error dialog box
If the Details button is available, copy its content as well.
(6) Collecting RAS information
If a problem occurs during remote monitoring, collect RAS information on the manager host and monitored host.
How to collect the information differs depending on the method of connecting monitored hosts. For collecting information from remotely-monitored hosts, the connection method differs depending on the log information to be collected and the OSs on the manager host and monitored hosts. For details about the connection methods for remote monitoring, see 7.6.2 Collectable log information and connection methods for remote monitoring in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.
The following describes how to collect information when the OS on the manager host is UNIX.
Connection method |
Host for collecting information (OS) |
References about the collection method |
---|---|---|
SSH connection |
Manager host (UNIX) |
Table 11-27 Collecting data on the UNIX manager host (for SSH connection) |
Monitored host (UNIX) |
Table 11-28 Collecting data on the UNIX monitored host (for SSH connection) |
(a) For SSH connection
The following table describes how to collect data on the manager host (UNIX) if a problem occurs in SSH connection.
No. |
Procedure |
---|---|
1 |
From the console, execute the following commands, and then collect the results:
|
2 |
Collect the authentication information for SSH connection.
|
3 |
Collect the data indicating that an SSH connection with the remotely-monitored host was successfully established by using the private key placed on the host. |
The following table describes how to collect data on the monitored host (UNIX) if a problem occurs in SSH connection.
No. |
Procedure |
---|---|
1 |
Log in to the monitored host as the monitored user, execute the following commands from the console, and then collect the results:
|
2 |
Collect the following files:
|