Fibre Channel Adapter Testing Prerequisites
Tests for driver certification include manual and automated test cases. All automated and manual tests must pass for certification.
This section describes the tasks that you must complete before you test a Fibre Channel storage controller by using the Windows Hardware Lab Kit (Windows HLK):
Manual test cases
Automated tests
Hardware Requirements
The following hardware is required for testing a Fibre Channel storage controller. You might need additional hardware if the test device offers other features. To determine whether additional hardware requirements apply, see the test description for each test that appears for the device in Windows HLK Studio.
Note
With the exception of the test computer and test controller, all hardware involved in the test must already have a logo.
One test computer. The test computer must meet the Windows HLK requirements. For more information, see Windows HLK Prerequisites.
One Fibre Channel RAID storage subsystem that can support any one of the following: RAID-0, RAID-1, RAID-5, RAID-10, or RAID-6.
Warning
Do not test by using a storage subsystem that connects via MPIO.
If the Fibre Channel adapter is not bootable, one ATA or SCSI controller.
If the Fibre Channel adapter is not bootable, one ATA or SCSI disk drive. The disk must have at least 18 GB of space.
One bootable floppy disk drive.
One floppy disk.
Two identical PCI-X or PCIe-based Fibre Channel adapters (the test devices).
Two (or three, if testing RAID-5) Fibre Channel hard disk drives or Fibre Channel JBOD.
One PCI-to-PCI bridge adapter.
One PCI-to-PCI bridge adapter, unless any of the following conditions apply:
The controllers cannot fit into PCI bridge adapters. This may occur if the controllers are integrated controllers or if the controllers can only fit into specially designed slots.
The controller is designed and sold only for systems that cannot accept full height PCI-to-PCI bridge adapters, such as blade servers.
You can put one of the controllers into a PCI bus slot that is already behind a PCI bridge.
Note
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 devices, at least one computer in the pool must contain four processors and a minimum of 1 GB of RAM. Additionally, that computer must contain the device and the driver that you want to test. If 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 do not include a driver to test, such as hard disk drive tests, 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. Test personnel must 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 may not use any form of virtualization when you test physical devices and their associated drivers for server certification or signature. All virtualization products do not support the underlying functionality that is 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
The following software is required for testing a Fibre Channel storage controller:
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 current release of the Windows Driver Kit (WDK)
Test Computer Configuration
To configure the test computer to test a Fibre Channel storage controller, follow these steps:
When the test computer is turned off, complete the following assembly steps:
Install one CD drive in the test system, if the system does not already contain one.
Install one Fibre Channel adapter (Test Device 1).
Connect the Fibre Channel adapter to the RAID system.
If either of the following situations apply, connect two Fibre Channel hard disk drives or a Fibre Channel JBOD to the test device, and then skip to step G:
The Fibre Channel adapter test device is an integrated controller, there is only one of these controllers in the system, and an equivalent PCI adapter version of the device does not exist.
The Fibre Channel adapter is designed for and sold only in a host test system that accepts only a single version of the controller.
Note
Use three Fibre Channel hard disk drives for RAID-5 testing.
Install a PCI-to-PCI bridge in a PCI slot in the test system.
Note
You can also use an existing slot behind a bridge.
Install a secondary, identical Fibre Channel adapter (Test Device 2) in the PCI-to-PCI bridge card.
Connect two Fibre Channel hard disk drives or a Fibre Channel JBOD to Test Device 2.
Note
Use three Fibre Channel hard disk drives for RAID-5 testing.
Turn on the test computer.
Configure the JBOD or disks as Array 2, according to the following list:
If the test device supports only one RAID level, configure the JBOD or disks by using that level. Otherwise, configure the JBOD or disks to the RAID levels that are specified in the following table.
RAID levels that the test device supports Use RAID level 0 and 1
1
0 and 5
5
1 and 5
Either 1 or 5
0, 1, and 5
Either 1 or 5
- Array 2 must contain at least 60 GB of space.
10. Configure the RAID system as Array 1 according to the following list:
- If the RAID system supports only one RAID level, configure it by using that level. Otherwise, configure the RAID system according to the preceding table.
- Array 2 must contain at least 60 GB of space.
11. If the test Fibre Channel adapter is not bootable, install an ATA or SCSI hard disk drive and an alternate ATA or SCSI boot controller if they are not present.
Turn on the test computer, install the appropriate Windows operating system, install all available Windows updates, and then configure the computer for your test network. The test network is the network that contains the Windows HLK Studio and Windows HLK Controller.
Install any HBA or RAID system drivers that are necessary to connect to or manage the peripheral devices.
Do one of the following to install the operating system:
If the test Fibre Channel adapter is bootable, install the operating system on an NTFS, 364-GB partition on the RAID system.
Install the operating system on an NTFS-formatted, 36-GB partition on the ATA or SCSI hard disk drive that is connected to the alternate ATA or SCSI boot controller in the test system.
Start the test system in the Microsoft Windows operating system.
Use the Windows Disk Management utility to set up three 4 GB NTFS partitions on Array 1, as shown in the following diagram:
Use the Windows Disk Management utility to mirror one of the volumes created in step 6 to Array 2.
To set the system page file and enable crashdump, follow these steps:
Click the Start button, right-click My Computer, and then click Properties.
Click the General tab, and then note the amount of RAM that the computer contains.
Click the Advanced tab (or click Advanced system settings in the left pane for Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows Server 2008 R2 or Windows Server 2012), and then, in the Performance area, click Settings.
Note
If you are prompted to enter administrative credentials or allow the action, enter the credentials or allow the action.
Click the Advanced tab, and then, in the Virtual Memory area, click Change.
Select Custom Size, and then enter a number in the Initial size (MB) box that is larger than the size of RAM that you noted in step b.
In the Maximum size (MB) text box, enter a maximum size value that is larger than the initial size that you entered in the Initial size (MB) box. (The maximum size is typically 1.5 to 2 times the initial size.)
Click Set, and then click OK two times.
Click OK, and then restart the computer to update the page file size.
Copy the Windows symbol files to %SystemDrive%\Symbols.
Verify that Windows can access the Fibre Channel storage 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.
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).