iSCSI Target Oneway CHAP Test (LOGO)
This test verifies that the target device (disk, tape, or optical storage device) can use the Challenge Handshake Authentication Protocol (CHAP) authentication mechanism.
|Expected run time (in minutes)||5|
|Timeout (in minutes)||300|
|Requires special configuration||false|
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 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).
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.
For troubleshooting information, see Troubleshooting Device.Storage Testing.
Look at the job results log file for test failures.
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).
This test always return Pass or Fail. To review test details, review the test log from the Windows HLK Manager.
The test uses multiple variations to verify that a target properly supports one-way CHAP. The first variation performs a logon similar to the user logging in through iSCSI Initiator Control Panel. The rest of the variations perform logon outside of the Microsoft initiator by using the iSCSI protocol. Each variation receives the challenge from the target and responds to the targets with a calculated response. The target is then expected to either continue with the iSCSI logon or return the appropriate status code, depending on the response received.
There are four different variations:
Valid response is returned using hexadecimal encoding
Valid response is returned using base64 encoding
Invalid response is returned using hexadecimal encoding
Invalid response is returned using base64 encoding
To run this test:
Run the test as a Driver Test Manager (DTM) job.
Enter the required data in the configuration dialog box that appears when this job is scheduled
iscsi_targetchap -oneway -hct -v [LogVerbosity]
Runs the test.
For command-line help for this test binary, type /h.
|Parameter name||Parameter description|
|LLU_NetAccessOnly||User account for accessing test fileshare.|
|LLU_LclAdminUsr||User account for running the test.|
|LogVerbosity||Vebosity of logging. There are three levels of output 0,1,2 where 2 is the most verbose.|