Fcoe boot issues, Option rom known issues, Windows known issues – Dell Intel PRO Family of Adapters User Manual
Page 48
.
ANS teaming will work when NLB is in multicast mode, as well. For proper configuration of the adapter in this mode,
.
FCoE and TCP/IP traffic on the same VLAN may not work on some switches
This is a known switch design and configuration issue.
Reboot Prompt Appears when modifying the Performance Profile
In Microsoft* Windows Server*, after modifying the performance profile, a reboot prompt may appear. The Intel®
Ethernet FCoE boot was configured and there is no need to reboot. The base driver reloads are blocked if FCoE boot is
configured and the system is connected to an FCoE target, even if the system was booted locally.
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
Brocade switch support in Release 16.4
Intel® Ethernet FCoE does not support Brocade switches in Release 16.4. If necessary, please use Release 16.2.
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:
Crash dump to an FCoE disk if the Windows directory is not on the FCoE Boot LUN.
Use of the DedicatedDumpFile registry value to direct crash dump to another FCoE LUN.
Stopping the Intel DCB service may cause the OS to hang or crash.
Do not stop the DCB service if the system is FCoE booted.
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 Intel® Ethernet 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, 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 (for example, Data Center Tab is greyed out) but kernel level drivers have not been