iSCSI Target Ping Test (LOGO)
This test verifies that iSCSI targets can send and receive ping requests. Because there is no standard mechanism for initiating the sending of ICMP echo messages on a target, manual interaction is required to complete the test.
Test details
| Specifications |
|
| Platforms |
|
| Supported Releases |
|
| Expected run time (in minutes) | 5 |
| Category | Development |
| Timeout (in minutes) | 300 |
| 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 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.
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 returns Pass or Fail. To review test details, review the test log from the Windows HLK Manager.
More information
This test operates in two phases:
The first phase verifies that iSCSI targets respond to ping requests by sending an ICMP echo packets to the target by using a network card in the test system.
The second phase verifies the target can send ICMP echo packets to another address, which in this case is the network adapter in the test system.
If you can do a ping operation from the storage management UI, skip to step 5. Otherwise, go to step 2.
Telnet into the target: telnet <target portal address, e.g. 10.10.20.80>
For the telnet console IP address, it may be different from the target portal address, but it should be another portal address of the same target, such as 10.10.20.82. You can check all the network interfaces or use the network monitor to send requests to find it.
Change the PortalIPAddress under [Target1] in iscsihctconfig.ini to be the one received in step 3.
Run the Ping Test on the test client and ping the initiator IP address from the telnet console or storage management UI.
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.
Command syntax
| Command option | Description |
|---|---|
Iscsi_pingtest.exe -target -hct -v [LogVerbosity] |
Runs the test. The -v option controls the verbosity of the logging. There are three levels of output (0, 1, and 2) where 2 is the most verbose. |
Note
For command-line help for this test binary, type /h.
File list
| File | Location |
|---|---|
Iscsi_pingtest.exe |
<[testbinroot]>\nttest\driverstest\storage\wdk\iscsi\ |
Parameters
| 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. |