D.5 express_diag(Diagnosis of Express Manager environment)

This section explains the command for diagnosing Express Manager environment.

NAME

express_diag - Diagnosis of Express Manager environment.

SYNOPSIS

$INS_DIR\Express\Manager\bin\express_diag

($INS_DIR means "Program Directory" specified at the Express Manager installation.)

DESCRIPTION

Express Manager environment is diagnosed and the result is output to stdout. To execute the command, operating system administrator privileges are required.

The output format is as follows.

Component
   test name : result
   test name : result
   ...
Component
   test name : result
   test name : result
   ...

The following table shows the meanings of the information displayed.

Title	Explanation
Component	Displays a component name. Any of the following names is displayed. Express Web GUI Express Manager Storage Cruiser Manager
test name	Displays a test name. Either of the following test names is displayed. <service name> service/daemon test Checks whether service/daemon of <service name> is booted. <file name> file test Checks whether the file of <file name> exists.
result	Displays a test result. Either of the following results is displayed. Passed Indicates that the test has been passed. Failed Indicates that the test has not been passed or has failed for some reason.

Title

Explanation

Component

Displays a component name. Any of the following names is displayed.

Express Web GUI

Express Manager
Storage Cruiser Manager

test name

Displays a test name. Either of the following test names is displayed.

<service name> service/daemon test
Checks whether service/daemon of <service name> is booted.
<file name> file test
Checks whether the file of <file name> exists.

result

Displays a test result. Either of the following results is displayed.

Passed
Indicates that the test has been passed.
Failed
Indicates that the test has not been passed or has failed for some reason.

In the event that the test result of service is "Failed":
Open [Control panel] - [Management tool] - [Service] to check the service displayed in <service name>.
- In the event that the service of <service name> is stopped:
  Start the service.
- In the event that the service of <service name> is not displayed:
  Express Manager environment may have been destroyed.
  Collect the required material to solve the trouble from the output results of this diagnostic tool and "D.4 express_managersnap (Collecting Express Manager troubleshooting information)"and then contact a Fujitsu system engineer (SE).
In the event that the test result of file is "Failed":
There is the case that a test result becomes "Failed" of the file by just after the installation of Express Manager or a function to use.
- contact.db
  When setting of 'specifying contact information for trouble occurrence' is not considered to be it, this file is not made.
- property.db
  When setting of 'Information Managed with Express' is not considered to be it, this file is not made.
  - History information (Number of days kept, File Size)
  - Screen update information
  - E-mail Information (mail configuration information, mail destination information)
- array.db
- manager.db
- alias.db
  'ETERNUS SF Express Manager' service never stops, and non-registration a disk storage system, these files are not made.
- user.db
  When non-registration a disk storage system, this file is not made.
- server.db
  When not additional server information, this file is not made.
- ConfigurationChangeDB.xml
  When operation to become the save object of 'Configuration change history' is not performed, this file is not made.
  - History information (Number of days kept, File Size)
  - Screen update information
  - E-mail Information (mail configuration information, mail destination information)
  - Registering Disk Storage Systems
  - Registering server information
- LoginLogoutDB.xml
  When login to Express Web GUI is never performed, this file is not made.
- EventDB.xml
  When not receiving SNMP Trap from disk storage system, and when not executing Copy Control Module by Express Web GUI, this file is not made.
When use a function, but the test result of the file becomes "Failed", Express Manager environment may have been destroyed.
In the event that the trouble is still not solved despite of some actions or some trouble is occurring though no failure is not detected by this diagnostic tool, collect the required material to solve the trouble from "D.4 express_managersnap (Collecting Express Manager troubleshooting information)" and then contact a Fujitsu system engineer (SE).

EXAMPLES

> express_diag
Express Web GUI
    'ETERNUS SF Express Apache Service' service/daemon test : Passed
    'ETERNUS SF Express Tomcat Service' service/daemon test : Passed
    'httpd.conf' file test : Passed
    'express.xml' file test : Passed
Express Manager
    'ETERNUS SF Express Manager' service/daemon test : Passed
    'contact.db' file test : Passed
    'property.db' file test : Passed
    'array.db' file test : Passed
    'manager.db' file test : Passed
    'user.db' file test : Passed
    'alias.db' file test : Passed
    'server.db' file test : Failed
    'ConfigurationChangeDB.xml' file test : Passed
    'LoginLogoutDB.xml' file test : Failed
    'EventDB.xml' file test : Passed
Storage Cruiser Manager
    'ETERNUS SF Storage Cruiser Manager' service/daemon test : Passed
    'SNMP Trap Service' service/daemon test : Passed
    '1_3_6_1_4_1_211_4_1_1_126_1_60.xml' file test : Passed
    '1_3_6_1_4_1_211_4_1_3_21_1.xml' file test : Passed
    '1_3_6_1_4_1_211_4_1_3_21_3.xml' file test : Passed
    '1_3_6_1_4_1_347.xml' file test : Passed
    'Trap.bat' file test : Passed