iSCSI Target Mutual 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.
Test details
Associated requirements |
Device.Storage.Hd.Iscsi.BasicFunction |
Platforms |
Windows 7 (x64) Windows 7 (x86) Windows 8 (x64) Windows 8 (x86) Windows Server 2012 (x64) Windows Server 2008 R2 (x64) Windows Server 2008 x64 Windows Server 2008 x86Windows 8.1 x64Windows 8.1 x86Windows Server 2012 R2 |
Expected run time |
~5 minutes |
Categories |
Certification Functional |
Type |
Manual |
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 HCK client, or if there is no iscsihctconfig.ini under [HCK Path]\JobsWorkingDir\ on the HCK 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 troubleshooting information, see Troubleshooting Device.Storage Testing.
In addition:
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 HCK Manager.
More information
The test uses multiple variations to verify that a target properly supports mutual CHAP. The first variation performs a logon similar to the user logging on through iSCSI Initiator Control Panel Applet. The rest of the variations perform logon outside of the Microsoft initiator by using the iSCSI protocol. Each variation challenges the target by using different challenge sizes with different encodings. The target is expected to calculate the proper response.
There are four different variations:
Challenge size of 1 byte using hexadecimal encoding
Challenge size of 1 byte using Base64 encoding
Challenge size of 1024 bytes using hexadecimal encoding
Challenge size of 1024 bytes using Base64 encoding
To run this test:
Set up the initiator and the target with CHAP secrets.
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.
Parameters
| Parameter | Description |
|---|---|
LogVerbosity |
The verbosity of logging. There are three levels of output: 0, 1, and 2. 2 is the most verbose. Default value: 1 |
Command syntax
| Command option | Description |
|---|---|
iscsi_targetchap -mutual -hct |
Runs the test. |
Note
For command-line help for this test binary, type /h.
File list
| File | Location |
|---|---|
Iscsi_targetchap.exe |
<[testbinroot]>\nttest\driverstest\storage\wdk\iscsi |