iSCSI HBA Testing Overview

The procedures that are presented in this section outline the process for testing your iSCSI host bus adapter (HBA) for correct functionality with the Microsoft Windows operating system. These procedures use the Windows Driver Kit (WDK) and Driver Test Manager (DTM). To ensure full functionality, you must run all of the tests that DTM identifies as required for the device. If your product provides bus-specific support, you must run the appropriate bus-specific tests in addition to the standard tests.

The test procedures in this section are divided into the following types of topics:

  • Overview: The overview topics describe the hardware, software, and tester knowledge requirements.
  • Preparing: The preparing topics describe how to configure the system or systems for "Designed for Windows" logo testing.
  • Running: The running topics describe how to run the tests for your device or system.
  • Troubleshooting: The troubleshooting section provides information to diagnose failures, warnings and/or errors with the test.


The following list contains all of the tests that you might need to run to obtain a logo for your test device, depending on the capabilities of the device or system that you are testing.

The following tests require user intervention, so you must run them individually:

The following tests are automated, so you can run them in a group:

Run time: approximately 3 days

Hardware Requirements

You can run the iSCSI HBA tests in a single configuration. However, you can implement this configuration in one of two ways:

  1. An iSCSI HBA, iSCSI disk storage system, and iSCSI tape medium changer
  2. An iSCSI HBA, a bridge to another bus, a disk storage system, and tape medium changer

The following hardware is required for iSCSI HBA testing.

  • Dual-core or equivalent processor (Windows Client Operating Systems)

    Note  An equivalent processor is any processor that appears to Windows as containing the specified number of CPUs. This can be achieved through one or more physical microprocessors.

  • Quad-core or equivalent processor (Windows Server Operating Systems)

    Note:  An equivalent processor is any processor that appears to Windows as containing the specified number of CPUs. This can be achieved through one or more physical microprocessors.

  • 2 GB memory (Windows Client Operating Systems)
  • 6 GB memory (Windows Server Operating Systems)
  • For Windows Server 2008 only: If the test system does not have a second instance of the test adapter installed, then a second system is required. The second system must also meet the processor and memory requirements for Windows Server 2008 server testing. The second system should contain one instance of the test adapter connected to any storage device. The second system should not be setup to boot from the test adapter. Also, the storage device connected to the test adapter should not be setup to contain any portion of the page file. The storage adapter procedures require you to connect two identical HBA(s). Select the device you are not booting from when running the Dynamic Partitioning test using the device console submission view. If two identical HBA(s) cannot be placed in the system because the device is integrated, add two machines with identical HBA(s) to the machine pool and run the Dynamic Partitioning test against the machine with a test HBA you are not booting from. In this machine, you should be booting off an additional non test controller.
  • An iSCSI HBA (the test device).
  • One combination tape drive and medium changer device. This device must be an iSCSI device if you are testing without a bridge or a device that connects through another bus if you are testing with a bridge.
  • Two disk storage systems. These system must be iSCSI disk storage systems if you are testing without a bridge or disk storage systems that connect through another bus if you are testing with a bridge.

    Note  If the test device supports boot, you need two disk targets. These targets can exist on the same disk storage device, if they have different target names.

  • An iSCSI bridge, if you are testing in a configuration with a bridge.
  • Three blank media cartridges for each drive on the medium changer device.
  • A monitor, keyboard, and mouse.
  • A boot-capable floppy disk drive, if your device supports boot.
  • Two 1-Gb network adapters.

Important  All hardware (except the test device) must be included in the Bb961559.internet_link_sm(en-us,MSDN.10).gifMicrosoft Windows Marketplace.

Note  Testing a device to obtain a logo for Server Device qualification requires that the system being used to test the device supports four processors and a minimum of 1 GB of RAM. These system capabilities are required for the "Dynamic Partitioning (DP) Simulator and Test" and the "Multiple Processor Group" test to run. You do not need a system that actually supports DP capabilities or has greater than 64 processors to test your device.

If a pool of systems is used to test devices, at least one system in the pool must contain four processors and a minimum of 1 GB of RAM. Additionally, that system must contain the device and driver being tested. As long as the driver is the same on all systems in the pool, the schedule will be created to run against all systems.

For those tests that do not include a driver to test, such as testing a hard drive, the Driver Test Manager (DTM) scheduler will constrain the DP test to run on the default system. This system should also be manually configured to have multiple processor groups. The default system is the first one listed. Test personnel, in this case, should ensure that this first system meets these minimum hardware requirements.

Note  Except for Para-Virtualization drivers (as defined by Logo Requirement Policy-0020), physical devices and their associated drivers being tested for Server Logo or Signature may not be tested in virtual machines using any form of virtualization. This is because not all virtualization products support the underlying functionality needed to pass the tests relating to Multiple Processor Groups, Device Power Management, Device PCI functionality, etc.

Software Requirements

The following software is required to run the iSCSI HBA tests:

  • One of the following operating systems:
    • Microsoft Windows Vista
    • Microsoft Windows XP Professional with Service Pack 2 (SP2)
    • Microsoft Windows Server 2003, Enterprise Edition, with Service Pack 1 (SP1)
    • Microsoft Windows Server 2003, Datacenter Edition, with SP1
    • Microsoft Windows Server XP Professional x64 Edition
    • Microsoft Windows Server 2003, Enterprise x64 Edition
    • Microsoft Windows Server 2003, Datacenter x64 Edition
    • Microsoft Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems
    • Microsoft Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems
    • Microsoft Windows Server 2008 R2

  • Any drivers that are not shipped with the operating system
  • The current release of the Windows Driver Kit (WDK)
  • The latest version of the iSCSI software initiator (if the operating system is not Windows Vista).

    Note  To download the iSCSI software initiator, search for "iSCSI software initiator" in the Bb961559.internet_link_sm(en-us,MSDN.10).gifMicrosoft Download Center.

  • The Microsoft .NET Framework Version 1.1. You can get .NET 1.1 from the Bb961559.internet_link_sm(en-us,MSDN.10).gifMicrosoft Download Center.

Tester Knowledge Requirements

To run the iSCSI HBA tests, testers must know how to:

  • Set up an iSCSI environment and record the Internet Protocol (IP) addresses and target names of the devices.
  • Set the secret for one-way and mutual CHAP (if supported).
  • Log on to iSCSI target devices.
  • Format and partition a hard disk drive.
  • Install the operating system from the product CD

This section includes:

Troubleshooting iSCSI HBA Tests

Related Links

Send feedback on this topic
Built on December 10, 2009