iSCSI Target Digest Test (Disk) (LOGO)
This test verifies that an iSCSI disk storage system supports header and data digests as negotiated during the logon phase.
Test details
Specifications |
|
Platforms |
|
Supported Releases |
|
Expected run time (in minutes) | 40 |
Category | Development |
Timeout (in minutes) | 2400 |
Requires reboot | false |
Requires special configuration | false |
Type | automatic |
Additional documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):
Running the test
Before you run the test, complete the test setup as described in the test requirements: iSCSI Boot Component Testing Prerequisites.
If this is the first time you are running an iSCSI HBA test, iSCSI Target test, or MPIO test over iSCSI bus type on the HLK client, or if there is no iscsihctconfig.ini under [HLK Path]\JobsWorkingDir\ on the HLK client, you will receive a pop-up dialog box to input iSCSI configuration information and/or HBA information. For more information about this dialog box, see "Running the test" in iSCSI HBA Boot Test (LOGO).
Troubleshooting
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.
For troubleshooting information, see Troubleshooting Device.Storage Testing.
This test returns Pass or Fail. To review test details, review the test log from the Windows HLK Manager.
In addition:
Look at the job results log file for test failures
Verify the target has been formatted and assigned a drive letter.
Enter the required data in the configuration dialog box that appears when this job is scheduled. For more information, go to iSCSI HBA Boot Test (LOGO).
More information
The test performs the following algorithm:
Prepares the system for iSCSI operations:
If the target that is used for testing is already logged on, the session information is saved so the session can be restored later.
The target disk device is added as a static iSCSI target.
Perform iSCSI operations
If the target that is used for testing is already logged on, the current session to the target is logged out
The target is logged on with header digests enabled.
After logging on to the target, the test waits for all disk devices to be enumerated on the test system.
The test will perform I/O read and write operations with the current target session.
The test repeats the preceding steps with data digests only enabled and header and data digests enabled.
The target that you are testing must permit logon by using all three digest combinations and no I/O failures can be detected during I/O operations
Restore any previous iSCSI target sessions.
To run this test:
Log on to the disk target and format the drive. The disk target should have a drive letter before you run the test.
Run the test as DTM job from the Device Console window.
Enter the required data in the configuration dialog box that appears when this job is scheduled.
Command syntax
Command option | Description |
---|---|
iscsi_digest.exe -hct [TestType] [TargetType] -cleanup -v [LogVerbosity] |
Runs the test. |
-hct [TestType] |
The options that can be set are -target or -hba. |
[TargetType] |
Runs the test against an iSCSI disc. The -disk parameter sets this option. |
-setup or -login [DigestType] or -logout [DigestType] |
Runs the test with the digest type option set. The digest type option values are header, data, or both. |
-v [LogVerbosity] |
Sets the test result logging level. This option sets the verbosity of the logging. There are three levels of output: 0, 1, and 2. 2 is the most verbose. |
Note
For command-line help for this test binary, type /h.
File list
File | Location |
---|---|
Iscsi_digest.exe |
<[testbinroot]>\nttest\driverstest\storage\wdk\iscsi\ |
Parameters
Parameter name | Parameter description |
---|---|
TestType | -target or -hba |
TargetType | -disk or -tape |
LLU_LclAdminUsr | User account for running the test. |
StorageDriveLetter | Drive letter of a volume on the target disk |
WDKDeviceID | Instance path of device to test |
LogVerbosity | Vebosity of logging. There are three levels of output 0,1,2 where 2 is the most verbose. |