# Known Issues

## Windows Issues

- Options on the Data Center tab of the adapter's Device Manager property sheet are grayed out.

You cannot disable DCB or modify any DCB settings while the system is booted from an FCoE drive or if the system paging file is on an FCoE drive.

- Windows Server 2008 with Hyper-V - storage miniport driver does not load when an adapter is added or removed as a VNIC

  In Windows Server 2008 with Hyper-V, the storage miniport driver may not automatically load after adding or removing a DCB/FCoE adapter as a shared external virtual device. To load the storage miniport driver, reset the adapter.

- When installing FCoE after installing ANS and creating AFT Team, Storports are not installed

> If the user installs ANS and creates an AFT team and then installs FCoE/DCB, the result is that DCB is off by default. If the user then enables DCB on one port, the OS detects Storports and the user must manually click on the new hardware wizard prompts for each of them to install. If the user does not do that, DCB status is non-operational and the reason given is no peer.

- Creating ALB teaming causes loss of FCoE links in teamed interfaces; only one interface keeps FCoE link

> After an ALB team is created, all but one of the FCoE interfaces will lose its FC link. Removing the ALB team from the FCoE interface will bring the FC link back up.

- Link Aggregation teams are not supported with existing FCoE Switches

- Intel® PROSet for Windows Device Manager (DMiX) is not synched with FCoE CTRL-D Utility

> When the user disables FCoE via the Control-D menu, the Intel PROSet for Windows Device Manager User Interface states that the flash contains an FCoE image, but that the flash needs to be updated. Updating the flash with the FCoE image again, re-enables FCoE and returns the user to the state where all the FCoE settings are available.

> If the user uses the control-D menu to disable FCoE, then they should use the control-D menu to enable it because Intel PROSet for Windows Device Manager does not support enabling or disabling FCoE.

- Hyper-V

> Virtual Machine Queue (VMQ) and FCoE/DCB cannot co-exist on the same port. When VMQ is enabled on the Physical adapter, if FCoE/DCB is present on that port, DCB will enter a non-operational state and FCoE will not function properly. FCoE and DCB functionality will return back to normal once VMQ is disabled.

- 82599-based adapters don't display as SPC-3 compliant in Windows MPIO configuration

> Because the FCoE initiator is a virtuliazed device it does not have its own unique hardware ID and thus is not displayed as a SPC-3 compliant device in Windows MPIO configuration.

## FCoE Boot Issues

#### Option ROM Known Issues

- Discovery problems with multiple FCoE VLANs

> The FCoE Option ROM may not discover the desired VLAN when performing VLAN discovery from the Discover Targets function. If the Discover VLAN box is populated with the wrong VLAN, then enter the desired VLAN before executing Discover Targets.

#### Windows Known Issues

- Upgrading or uninstalling driver will cause blue screen

> Upgrading or uninstalling the network adapter driver via Windows Device Manager on the boot port will result in a lost connection to the SAN. The lost connection will result in a Windows blue screen on the next boot and will require the OS to be reinstalled.

- Windows uses a paging file on the local disk

> After imaging, if the local disk is not removed before booting from the FCoE disk then Windows may use the paging file from the local disk.

- Crash dump to FCoE disks is only supported to the FCoE Boot LUN

> The following scenarios are not supported:

> o Crash dump to an FCoE disk if the Windows directory is not on the FCoE Boot LUN.

> o Use of the DedicatedDumpFile registry value to direct crash dump to another FCoE LUN.

- Stopping the IntelDCB service may cause the OS to hang or crash

- FCoE uninstall from a local disk may be blocked because installer inaccurately reports system is booted from FCoE

> When the FCoE Option ROM connects to an FCoE disk during boot, the Windows installer may be unable to determine if the system was booted from FCoE or not and will block the FCoE uninstall. To uninstall, configure the Option ROM so that it does not connect to an FCoE disk.

- Unable to create VLAN interfaces with FCoE Boot enabled

  When booted with FCoE, a user cannot create VLANs and/or Teams for other traffic types. This prevents converged functionality for non-FCoE traffic.

- Server adapter configured for FCoE Boot available as External-Shared vnic via Hyper-V

  If a port is set as a boot port, when the user installs the Hyper V role in the system and then goes into the Hyper V Network Manager to select which port to externally virtualize, the boot port displays, which it should not.

  When setting the port to a boot port in Intel PROSet for Windows Device Manager (DMIX), a message shows that the user should restart the system for the changes to be effective but does not force a restart. As a result the user level applications are in boot mode (i.e., Data Center Tab is greyed out) but kernel level drivers haven’t been restarted to indicate to the OS that the port is a boot port. When the user then adds the Hyper V service to the system, the OS takes a snap shot of the ports available and this is the snap shot that it uses after the Hyper V role is added, system restarted and the user goes into the Hyper V Virtual Network Manager to virtualize the ports. As a result, the boot port also shows up.

  Solutions:

  Restart the system after setting a port to a boot port and before adding the Hyper V role. The port does not appear in the list of virtualizable ports in the Hyper V Virtual network manager.

  Disable/enable the port in Device Manager after setting it to boot and before adding the Hyper V role. The port does not appear in the list of virtualizable ports in the Hyper V Virtual network manager.

`Last modified on 12/10/10 3:04p Revision 20`