Windows OS Issues

The following issues are known to exist with Intel's Fibre Channel Over Ethernet (FCoE) software. These issues were not fixed as of the release of this document. Ensure that you obtain the latest information about known issues at the Intel FCoE documentation site.

Adding or Removing an Adapter as a VNIC Does Not Load the Storage Miniport Driver

When the Windows Server 2008 OS is installed with Hyper-V, the storage miniport driver might not automatically load after adding or removing a DCB/FCoE adapter as a shared external virtual device.

Workaround: Reset the adapter to load the storage miniport driver.

Installing the FCoE Image After Installing ANS and Creating AFT Teams Does Not Install Storports

If you install ANS and create an AFT team before you install FCoE or DCB, DCB is turned off by default. If you then enable DCB on one port, the OS detects Storports, and you must manually click on the new hardware wizard prompts for each port. If you do not manually enable each port, the DCB status will be nonoperational, and the given reason will be the absence of a peer (that is, no peer).

Link Aggregation Teams Are Not Supported

The current release of the FCoE software does not support link aggregation teams.

Using the FCoE CTRL-D Utility Is Not Possible With the Windows Device Manager

The Windows Device Manager is not synched with the FCoE CTRL-D utility. When you disable FCoE by using the Control-D menu, the Intel PROSet for Windows Device Manager indicates that the flash memory contains an FCoE image and that the flash memory needs to be updated. If you update the flash memory with the FCoE image, FCoE is re-enabled, and the system returns to the state in which all of the FCoE settings are available.

If you use the Control-D menu to disable FCoE, then you should use the Control-D menu to enable FCoE, because the Intel PROSet for Windows Device Manager does not support enabling or disabling FCoE.

Displaying 82599-Based Adapter Is Not Possible in Windows MPIO Configurations

As of this release, 82599-based adapters do not display as SPC-3 compliant in Windows MPIO configurations. The FCoE initiator is a virtualized device, so the initiator does not have its own unique hardware ID. Thus, the initiator is not displayed as an SPC-3 compliant device in a Windows MPIO configuration.

Removing ALB Teaming Causes All FCoE Functions to Fail

When this issue occurs, all Windows Device Manager windows tabs are grayed out, and both adapter ports fail.

For ANS teaming to work with the Microsoft Network Load Balancer (NLB) in unicast mode, the team LAA must be set to cluster node IP. For the ALB mode, you must disable Receive Load Balancing. For further configuration details, refer to the following URL:

http://support.microsoft.com/?id=278431

ANS teaming also works when NLB is in multicast mode. For instructions on how to configure the adapter in the multicast mode, refer to:

http://technet.microsoft.com/en-ca/library/cc726473(WS.10).aspx

FCoE and TCP/IP Traffic

On some switches, FCoE and TCP/IP traffic might not work. This is a known switch design issue.

Ethernet Virtual Storage Miniport Driver Disappears From the Device Manager

The Ethernet virtual storage miniport driver might not appear in the device manager when the corresponding adapter is virtualized to create a new virtual network, delete an existing virtual network, or modify an existing virtual network.

Workaround: Remove all of the resource dependencies on the FCoE miniport driver before you make any changes to the Intel adapter for virtualization.