# Known Issues

## Windows Issues

- Options on the Data 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 2003 - dynamic disks not restored when LUNs return after being lost

  In Windows Server 2003 dynamic disks may be restored in the offline state due to a limitation of the operating system. If the dynamic disk is reported in a later part of OS initialization then it will be reported as offline. The disks appear as Offline because the dynamic disk drivers have already started and checked for any dynamic disks to make available.

  This issue is documented in Microsoft KB #244550.

- 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

## 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

- 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

- Uninstalling driver can cause blue screen

> Uninstalling the network adapter driver on the boot port will result in a Windows blue screen on the next boot and require the OS to be reinstalled.

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

`Last modified on 6/16/10 8:07p Revision 11`