Hardware-based RAID Systems (iSCSI) Testing Prerequisites
This topic describes the tasks that you must complete before you test an Internet SCSI (iSCSI) hardware-based RAID storage array by using the Windows Hardware Lab Kit (Windows HLK):
Hardware Requirements
To test an iSCSI hardware-based RAID array, you need the following hardware. You might need additional hardware if the test device offers other features. To determine whether additional hardware requirements apply, see the description for each test that appears for the device in Windows HLK Studio.
Note
All hardware (except the test device, monitor, keyboard, mouse, and floppy disk drive) must be listed in the Windows Catalog.
1 test computer that meets the Windows HLK requirements. For more information, see Windows HLK Prerequisites. In addition, this computer must include:
1 logo-compliant Advanced Configuration and Power Interface (ACPI) BIOS, with ACPI enabled by default.
Dual-core or equivalent processor and 4 gigabytes (GB) of memory for Windows client operating systems (for example, Windows 8, Windows 7, and Windows Vista).
Quad-core or equivalent processor and 6 GB of memory for Windows Server operating systems.
An equivalent processor is any processor that appears to Windows as if it contains the specified number of CPUs. You can achieve this status through 1 or more physical microprocessors.
1 iSCSI RAID storage system (the test device).
Note
The RAID system must be a single cabinet that consists of an array controller that's enclosed in an external subsystem with hard disk drives. Or it must be an external array controller that connects to a RAID JBOD. The RAID system can't consist of only a Peripheral Component Interconnect (PCI)-based controller and 1 RAID JBOD.
At least one 1-GB Ethernet network adapter or iSCSI host bus adapter (HBA).
One 1-GB Ethernet switch.
1 bootable Advanced Technology Attachment (ATA) or SCSI hard disk drive that has a minimum capacity of 36 GB.
To certify your product for use on servers, the test computer must support four processors and a minimum of 1 GB of RAM. These system capabilities are required to test the Rebalance, D3 State, and Multiple Processor Group functionality of the device and driver. You do not need a computer that actually has more than 64 processors to test your device. Additionally, the server system(s) being used for device or driver testing must have Server Core installed prior to testing. For more information see Windows Server Installation Options.
If you use a pool of test computers to test your device, at least 1 computer in the pool must contain 4 processors and a minimum of 1 GB of RAM. Additionally, that computer must contain the device and the driver that you want to test. As long as the driver is the same on all the computers in the pool, the system creates a schedule to run against all test computers.
For tests that don't include a driver to test, like tests for a hard disk drive, the Windows HLK scheduler constrains the tests that validate the device's and driver's Rebalance, D3 State, and Multiple Processor Groups functionality to run on the default test computer. You must manually configure this computer to have multiple processor groups. The default computer is the first test computer in the list. Make sure that the first test computer in the list meets the minimum hardware requirements.
Note
Except for para-virtualization drivers (as defined by the WHCP Policies and Processes document), you can't use any form of virtualization when you test physical devices and their associated drivers for server certification or signature. Virtualization products don't support the underlying functionality that's required to pass the tests that relate to multiple processor groups, device power management, device PCI functionality, and other tests.
Note
Multiple Processor Groups Setting You must set the value for the processor group size for Hardware Lab Kit testing of Windows Server 2008 R2 and later device drivers for certification. This is done by running bcdedit in an elevated command prompt window, using the /set option.
The commands for adding the group settings and restarting are as follows:
bcdedit.exe /set groupsize 2
bcdedit.exe /set groupaware on
shutdown.exe -r -t 0 -f
The commands for removing the group settings and rebooting are as follows:
bcdedit.exe /deletevalue groupsize
bcdedit.exe /deletevalue groupaware
shutdown.exe -r -t 0 -f
Note
Code Integrity Setting
The Virtualization Based Security feature (VBS) of Windows Server 2016 must be enabled using Server Manager first.
Once that has occurred, the following Registry key must be created and set:
HKLM\System\CurrentControlSet\Control\DeviceGuard
HypervisorEnforcedCodeIntegrity:REG_DWORD
0 or 1 (disabled, enabled)
Software Requirements
To test a hardware-based RAID array, you need this software:
The drivers for the test device.
The latest Windows HLK filters or updates.
Windows symbol files. These are available from the Symbol Files website.
The latest version of the Microsoft® iSCSI Software Initiator.
The latest version of Microsoft iSNS Server.
The Microsoft .NET Framework 1.1.
The iSCSI Software Initiator and the .NET Framework are available from the Microsoft Download Center.
Configuring the Test Computer
To configure the test computer to test your iSCSI RAID array, follow these steps:
Install the Gigabit Ethernet network adapter or iSCSI HBA in the test computer.
Connect the Gigabit Ethernet switch to a power supply.
Note
Don't connect the switch to any other network.
Connect the Gigabit Ethernet network adapter or iSCSI HBA in the test computer to the switch.
Connect the disk storage system to the switch.
Install the appropriate Windows operating system on the test computer (onto an NTFS-formatted partition that has at least 36 GB on the hard disk drive), and then configure the computer for your test network. The test network is the network that contains Windows HLK Studio and Windows HLK Controller.
If the test device supports Microsoft Multipath I/O (MPIO), install any multipath drivers and create connections and multiple sessions by selecting Enable Multi-Path I/O.
Download and install the .NET Framework 1.1.
Configure the target device to use one-way (target authenticates initiator) Challenge Handshake Authentication Protocol (CHAP).
If your device supports mutual CHAP, also configure the device to use mutual CHAP.
Note
When you configure the device to use CHAP, you must provide a password that's 12 to 16 characters long. If you're configuring the device to use both one-way CHAP and mutual CHAP, you must provide different passwords for the target and the initiator.
Log on to the target disk storage system with Persistent Login set.
Important
You must log on to the iSCSI target device that's used for testing, or the tests won't work properly.
For a multipath test environment, if multiple ports (IP addresses) relate to one storage target, you must make sure that at least 2 iSCSI sessions are connected through the IP address to during testing.
Click Start, and then click Run.
Type diskmgmt.msc, and then press Enter.
Make sure that the test disks are set as basic disks.
Create three NTFS-formatted partitions that are greater than 2 GB each and less than 4 GB each.
A single logon should display all of these partitions.
Install the iSNS software on the test system and configure the target to use the iSNS server.
If your device supports digest and you must configure it, configure the test device to support digest.
Bind your volumes in the Favorite Targets (Windows Vista) or Bound Volumes (Windows Server 2003) tab of iSCSI Initiator Properties.
Verify that the computer can read or write to the test RAID array.
Install the Windows HLK client application on the test computer.
Use Windows HLK Studio to create a computer pool, and then move the test computer to that pool.
Make sure that the test computer is in the ready state before you begin your testing. If a test requires you to set parameters before you run it, a dialog box will appear for that test. For more information, review the specific test topic.
Some Windows HLK tests require user intervention. When you're running tests for a submission, it's a best practice to run the automated tests in a block separately from manual tests. This prevents a manual test from interrupting the completion of an automated test.
Warning
When testing storage devices, we strongly recommend that you complete all Device Fundamentals tests before starting storage tests. Storage tests will reconfigure your test device, leaving the device in a state unsuitable to support Device Fundamentals tests. The following configurations provide steps to create volume on the storage test device. This is important to complete the Device Fundamental part of testing (DevFund).
Feature-Based Configuration
If your device supports any of the feature(s) in this section, please update the associated configurations steps in addition to the general interface-based configuration steps in the "Configuring the Test Computer" section. Minor modifications may be applicable depending on the specifics of your device form-factor.
See "Hardware-based Raid Systems (Fibre Channel, SAS, SCSI, Serial ATA) Testing Prerequisites" above for feature-based configuration. The features also apply to iSCSI Hardware RAID Array Systems.