Notes
This command runs a consistency check against a configuration database. All database records are
checked. Error data is written to a file in the data folder on disk automatically. You do not need to specify
an output file.
Executing a consistency check with the diagnosticType parameter set to a value other than filesystem
and with the sourceLocation parameter set to onboard can cause the operation to run for a long time.
This can have adverse effects on host I/O processing. This operation should be done only under direction
from the support organization.
Upon completion of the diagnostic test, the controller firmware returns one of these results:
v Diagnosis completed without errors. No ZIP file created.
v Diagnosis completed with errors. Refer to the ZIP file created at:
...\Install_dir\data\FirmwareUpgradeReports\timestamp_buildNo.zip
If the diagnostic test detects an inconsistency in the configuration database, the controller firmware
performs these actions:
v Returns a description of the inconsistency
v Saves a ZIP file containing raw binary data
The controller firmware saves the ZIP file to this location:
...\Install_dir\data\FirmwareUpgradeReports\timestamp_buildNo.zip
You can use the binary data to help determine the cause of the problem, or you can send the file
containing the binary data to a IBM Technical Support representative.
To stop the database configuration diagnostic test, use the stop storageSubsystem configDbDiagnostic
command.
In addition, you can start the database configuration diagnostic test through the storage management
software GUI; however, you cannot stop the database configuration diagnostic test through the storage
management software GUI. If you want to stop a running diagnostic test, you must use the stop
storageSubsystem configDbDiagnostic command
Start Storage Subsystem Diagnostic Data Capture
This command produces a storage subsystem diagnostic data capture.
Syntax
start storageSubsystem ddc controller [(a|b)]
Parameters
Parameter Description
controller This parameter specifies the controller from which to
produce the diagnostic data capture. Valid controller
identifiers are a or b, where a is the controller in slot A,
and b is the controller in slot B. Enclose the controller
identifier in square brackets ([ ]). If you do not specify a
controller, the storage management software returns a
syntax error.
Chapter 3. Script Commands 3-305
To Next Page
Loading...
Need help?
General