Fibre Channel Over Ethernet Testing

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.

Before running the Fibre Channel over Ethernet (FCoE) adapter tests, you must first configure the computer and install the operating system. This section tells you how to complete these steps.

Hardware Requirements

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.

The following hardware is required for FCoE testing:

  • Three identical PCI-X or PCIe-based dual-port FCoE adapters (the test devices)

  • If the adapter is single-ported, four identical FCoE adapters

  • Two computers that meet the general hardware requirements for all adapter or controller testing

  • One FCF (FCoE switch) that supports 10G/E bandwidth for FCoE traffic

    Note  FCF is installed with four available FCoE ports/SFP+, and one FC port/SFP+

  • Copper- or fibre-based FCoE cable and FC cable for the above ports

  • One Fibre Channel storage array system supports any one of the following: RAID-0, RAID-1, RAID-5, RAID-10, or RAID-6

  • If the FCoE adapter is not bootable, one on-board SATA or SAS controller

  • If the FCoE adapter is not bootable, one SATA or SAS disk drive for OS installation

Test System Assembly

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.

To assemble the test system, follow these steps:

  1. Turn off the test system(s).

  2. If the FCoE adapter is not bootable, configure an alternate SATA or SAS on-board boot controller.

  3. If they are not present, install a respective SATA or SAS hard disk drive.

  4. Install an FCoE adapter in Test System 1.

  5. Connect one of the FCoE port to the FCF.

  6. Install a second FCoE adapter in the Test System 1, and then connect both FCoE ports to the FCF.

    Note  If the adapter is single-ported, use two adapters for this step.

  7. Install an FCoE adapter in Test System 2.

  8. Repeat step 5.

  9. Connect the FCF to the storage array.

  10. Connect all of the management links on a separate network, as shown in the diagram below (management network not pictured):

  11. Create the Boot LUN, and configure LUN mapping on the storage array system.

    Note  The array should contain 120 GB of disk space (recommended) for SAN boot configuration. Please use the storage array vendor’s management interface.

  12. Create the Data LUN and configure LUN mapping on the storage array system.

    Note  Data should contain 4 GB of disk space. Please use the storage array vendor’s management interface.

    Note  Please refer to the following table for a mapping summary:

    Machine HBA Port LUN ID Size (GB)
    1 A Boot 1 120
    1 B
    1 A Data 0 4
    1 B Data 0 4
    2 A
    2 B

     

  13. Configure the ports and zoning on the FCF using the switch vendor’s management interface.

  14. Turn on the test systems.

Test System Configuration

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.

  1. Follow these steps to install the operating system for SAN Boot Configuration on Test System 1:
    1. Install any HBA or RAID system drivers that are necessary to connect to or manage the peripheral devices.

    2. If the test FCoE adapter is bootable, install the operating system onto a NTFS-formatted partition on the 120-GB disk on the RAID system.

      Note  Allow the Windows OS to create any reserved partition.

    3. If the adapter is not bootable, follow step 2 below.

  2. Follow these steps for non-SAN Boot Configuration on Test System 1 and Test System 2:
    • Install the operating system onto a NTFS-formatted partition on the SATA or SAS disk.

      Note  This disk should contain 120 GB of disk space (recommended) and must be connected to the alternate SATA or SAS boot controller in the test system.

  3. Start the test system in the Windows operating system.
  4. To set the system page file and enable crashdump for Test System 1 only, follow these steps:
    1. Click the Start button, right-click My Computer, and then click Properties.

    2. Click the General tab, and then note the amount of RAM of the computer.

    3. Click the Advanced tab or click Advanced system settings in the left pane, and then click Settings in the Performance area.

      Note  If you are prompted to Enter Administrative credentials or allow the action, enter the credentials or allow the action.

    4. Click the Advanced tab, and then click Change in the Virtual Memory area.

    5. 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.

    6. 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.

    7. Click Set, and then click OK two times.

    8. Click OK, and then restart the computer to update the page file size.

    9. Copy the Windows Symbol files to %SystemDrive%\Symbols.

  5. To configure MPIO for Test System 1 only, follow these steps:
    1. Install Windows MPIO feature through Server Manager.
    2. Restart the system.
    3. Use the Mpclaim.exe command line utility or edit the MPIO CPL (Control Panel) GUI interface to add the LUN ID to be claimed.
    4. Restart the system.
    5. Initialize the MPIO’ed LUN as a basic disk.
    6. Format the disk with NTFS and assign the drive letter.
  6. Install DTM client.

 

 

Build date: 9/14/2012