Hitachi

JP1 Version 12 JP1/SNMP System Observer Description, Operator's Guide and Reference


jp1ssolog.bat (Windows only)

Organization of this page

Format

jp1ssolog.bat [-col] [-d output-destination-directory-name] [<agent> ...]

Function

The jp1ssolog.bat command collects data for an error investigation upon occurrence of an error in SSO. This command is only for Windows.

This command creates a JP1SSO directory in the default directory or the directory specified for the -d option and outputs data to be collected in the created directory. If a JP1SSO directory already exists, it is deleted and a new JP1SSO directory is created.

The default output destination for the data to be collected is %TEMP%\jp1log. You can change the default output destination by editing this command (a batch file).

Option

-col

Collects data in $SSO_DB\Coll as data for an error investigation.

-d output-destination-directory-name

Specifies the output destination for the data to be collected by using either a relative or absolute path.

<agent> ...

Collects the results of executing the ping command on the specified monitoring server as data for an error investigation. Specify an IP address or host name for <agent>. If the specified IP address or host name is incorrect, or the monitoring server is not running, the return value of the command is 1.

Customize

This command is a batch file. You can customize the following items, if necessary:

If you want to change the default output destination

Edit the output file name in the following line:

set OUTPUTDIR=%TEMP%\jp1log

Usage example

Collected data list

The following table lists and describes the data for an error investigation to be collected:

Classification

Collection method

Acquired data

Main Information

Manual

An environment configuration chart (OS, IP address, No. of interfaces, and the product configuration and version of each terminal)

A memo about how an error occurred (details about the occurrence date/time, OS, host name, IP address, performed operations, and symptoms)

Event log file#1

Problem report and user dump#2

OS information

jp1ssolog.bat

Collected files

In %SystemRoot%\system32\drivers\etc

Command execution results

hostname

set

netstat -a

netstat -aon

netstat -r

net start

ipconfig /all

Registry information

In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\

In HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\

tasklist

msinfo32

netsh -c advfirewall show allprofiles

netsh -c advfirewall firewall show rule name=all verbose

SSO information

jp1ssolog.bat

Collected files

In SSO-installation-folder\conf folder

In SSO-installation-folder\log folder

In SSO-installation-folder\report folder

SSO-installation-folder\uCPSB\CC\web\containers\SSOConsole\logs

SSO-installation-folder\uCPSB\CC\web\containers\SSOConsole\usrconf

SSO-installation-folder\uCPSB\CC\web\containers\SSOConsole\work

SSO-installation-folder\uCPSB\httpsd\conf

SSO-installation-folder\uCPSB\httpsd\logs

SSO-installation-folder\uCPSB\CC\client\logs\system\ejbcl\CJW

SSO-installation-folder\uCPSB\CC\web\redirector\logs

In SSO-installation-folder\auditlog

SSO-installation-folder\tmp\ssoclustersetup.log (when applicable)

%windir%\Temp\HCDINST\P-2942-8RCL.LOG (when applicable)

%windir%\Temp\jp1cm2sso_installer.log (when applicable)

SSO-installation-folder\uCPSB\install.log (when applicable)

SSO-installation-folder\uCPSB\spkmanage.log (when applicable)

SSO-installation-folder\uCPSB\insresult.dat (when applicable)

SSO-installation-folder\Version.txt

SSO-installation-folder\ProductInfo.txt

Command execution results

ssostatus

ssoapcom -X 4095#3

ssocollectd -X 4095#3

ssocolmng -X 4095#3

ssorptd -X 4095#3

ssotrapd -X 4095#3

ssomapstatus -show -all

ssoapcom -F#3

ssocollectd -F#3

ssocolmng -F#3

A list of folders and files in the installation directory

dir /s SSO-installation-folder

jp1ssolog.bat

with the -col option specified

In SSO-installation-folder\databases\Coll

jp1ssolog.bat

with the IP address or host name of the monitoring server specified

Results of executing ping -n 5 on the specified monitoring server

NNMi information

Manual

Command execution results

ovstatus

#1

The procedure for collecting event logs is described below. Note that the procedure differs depending on the version of Windows.

To collect event logs (for Windows Server 2008 R2):

  1. Select Control Panel, Administrative Tools, and then Event Viewer.

  2. Select Windows Logs, and then each of Application, Security, and System, and click Action and then Save All Events As, and set Save as type to Text (Tab delimited) (*.txt) and save the file as the desired name.

To collect event logs (for Windows Server 2012 or later):

  1. Select Control Panel, Administrative Tools, and then Event Viewer.

  2. Select Windows Logs, and then each of Application, Security, and System, and click Action and then Save All Events As, and set Save as type to Text (Tab delimited) (*.txt) and save the file as the desired name.

#2

Manually collect a problem report when a daemon process stops due to an application error, and a user dump when a command process stops due to an application error.

The following is the procedure for collecting problem reports and user dumps.

To collect problem reports:
  1. Select Control Panel, Action Center, Maintenance, and then View reliability history.

    The Review your computer's reliability and problem history window appears.

  2. Select View all problem reports at the bottom.

    The list of problem reports is displayed.

  3. Double-click the corresponding problem.

    The details of the problem report are displayed.

  4. Click View a temporary copy of these files.

    A new window appears. Collect the files displayed in the window.

To collect user dumps:

Perform the following operations while the error dialog box is being displayed.

  1. Start the task manager.

  2. Click the Processes tab in the Windows Task Manager dialog box.

  3. Right-click the name of the process that stopped due to an application error and select Create Dump File.

    A dialog box indicating the output-destination path of the user dump appears. Collect the files in the output-destination path displayed in the dialog box.

#3

Data cannot be collected when the corresponding daemon process is not running.

Return values

0

Data collection is completed.

1

Part of the data could not be collected, but no problem exists.

4

Data collection failed (incorrect output-destination directory).

Notes