iSCSI Persistent Login Test

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

Type: Automated Test

Overview

The iSCSI Persistent Login test verifies the basic functionality of persistent logons and verifies that targets are logged on every time the operating system restarts.

Details

This test verifies that the Microsoft iSCSI initiator service is running on the system that you are testing. The test verifies that the host-bus adapter (HBA) driver properly returns the current list of registered persistent targets. The test attempts to add a disk target to the list of current persistent targets and then verifies that the target persists after the system restarts.

The test uses an additional application that is used to access the target after the system restarts. This test application, Hitdisk.exe, must be located in the working directory of the iSCSI Persistent test program.

Run Time:
Log File:
System Restart Required: No
Test Category:
Supported operating systems for Logo or Signature testing:
  • Windows Vista

  • Windows Server 2003

  • Windows XP

Program:

Requirements

Software Requirements

The test tool requires the following software:

  • Supported operating system (see list above)

  • Software components included with the device that is being tested

  • On operating systems before Windows Vista, the latest version of the Microsoft iSCSI software initiator

Hardware Requirements

The test tool requires the following hardware:

  • Device to be tested

  • Computer that meets the minimum software requirements

  • Windows keyboard

  • Two-button pointing device

  • Color display monitor capable of at least 1024 by 768 resolution, 32-bits per pixel, 60 Hz

  • Hard drive with a minimum of 20 GB available on partition C:

Processor

The test tool runs on the following processor architectures:

  • x86

  • x64

  • Itanium

Running iSCSI Persistent Login Test

To run this test, do the following:

  1. Log on to the disk target and format the drive. The disk target should have a drive letter before you run the test.

  2. Run the test as a Driver Test Manager (DTM) job.

  3. Enter the required data in the configuration dialog box that appears when this job is scheduled.

Command Syntax

Command optionDescription

iscsi_plogin -phase 1 -hct

 

Troubleshooting

  1. Look at the job results log file for test failures.

  2. Check if the target has a drive letter.

  3. Verify the data entered in the configuration dialog box when the job is scheduled from the Device Console window.

Code Tour

File Manifest

FileLocation

iscsi_plogin.exe

...\tests\%ARCHITECTURE%\nttest\driverstest\storage\wdk\iscsi

 

Test Assertions

1.1 The Microsoft ISCSI Initiator service must be installed.
Test Assertion GUID: 77ac12a0-c4d9-11da-94f4-00123f3a6b60
Windows Logo Program: STORAGE-0002 Storage host controllers and adapters comply with industry standards and Windows requirements
Additional Information: Test: The iSCSI Persistent Login test verifies that the Microsoft initiator service is running on the system that is being tested. Apply: The test uses the service control manager APIs to verify that the Microsoft iSCSI initiator service (iscsiexe.exe) is present and started. If the service is not already started, the test automatically starts the service. Expect: The HBA establishes a TCP/IP connection with the test target.
1.2 The HBA must successfully return a list of current persistent targets.
Test Assertion GUID: 77ac12a1-c4d9-11da-94f4-00123f3a6b60
Windows Logo Program: STORAGE-0002 Storage host controllers and adapters comply with industry standards and Windows requirements
Additional Information: Test: The test verifies that the HBA driver properly returns the current list of registered persistent targets. Apply: The test queries the iSCSI initiator service for the list of currently registered persistent targets by using the ReportIScsiPersistentLogins routine. Expect: The HBA driver successfully returns the current list of persistent targets registered with it.
1.3 The HBA must successfully add the test target as a persistent target.
Test Assertion GUID: 77ac12a2-c4d9-11da-94f4-00123f3a6b60
Windows Logo Program: STORAGE-0002 Storage host controllers and adapters comply with industry standards and Windows requirements
Additional Information: Test: The test attempts to add the disk target used for HCT testing to the list of current persistent targets. Apply: The test uses the LoginIScsiTarget routine with the IsPersistent parameter set to TRUE, indicating that the specified target should be added as a persistent target. Expect: The HBA driver successfully adds the persistent target and returns STATUS_SUCCESS to indicate this condition.
1.4 The HBA must report the test target in the list of persistent targets.
Test Assertion GUID: 77ac12a3-c4d9-11da-94f4-00123f3a6b60
Windows Logo Program: STORAGE-0002 Storage host controllers and adapters comply with industry standards and Windows requirements
Additional Information: Test: The test verifies that the HBA driver properly returns the current list of registered persistent targets. Apply: The test queries the iSCSI initiator service for the list of currently registered persistent targets using the ReportIScsiPersistentLogins routine. Expect: The list of persistent targets that the HBA returns includes the disk target added as a persistent target.
1.5 The test service must be started following reboot.
Test Assertion GUID: 77ac12a4-c4d9-11da-94f4-00123f3a6b60
Windows Logo Program: STORAGE-0002 Storage host controllers and adapters comply with industry standards and Windows requirements
Additional Information: Test: The test verifies that the HBA driver properly reestablishes a persistent target after the system is restarted. Apply: Before restarting, the test installs a test service that tries to access the disk target that is installed as a persistent target. This test service is made to depend on the iSCSI initiator service. Therefore, the test service should not start until the drive is available. Expect: The test service can read/write from the persistent volumes. The test service fails to start if it cannot access those volumes.

 

 

Build date: 9/14/2012

Community Additions

ADD
Show: