
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.
FCoE Linkdown Timeout fails prematurely when Remote Booted
If an FCoE-booted port loses link for longer than the time specified in the
Linkdown Timeout
advanced
setting in the Intel® Ethernet Virtual Storage Miniport Driver for FCoE, the system will crash.
Linkdown
Timeout
values greater than 30 seconds may not provide extra time before a system crash.
Windows fails to boot properly after using the image install method
The following situation may arise when installing Windows for FCoE Boot using the imaging method:
Windows boots successfully from the FCoE LUN when the local drive is installed, but when the local drive is
removed, Windows seems to boot, but fails before reaching the desktop.
In this case it is likely that the Windows installation resides on both the FCoE LUN and local drive. This can
be verified by booting from the FCoE LUN with the local drive installed, then comparing the drive letter in the
path of files on the desktop with the drive letter for the boot partition in Windows' Disk Management tool. If the
drive letters are different, then the Windows installation is split between the two disks.
If this situation is occurring, please ensure that
fcoeprep
is run prior to capturing the image, and that the
system is not allowed to local boot between running
fcoeprep
and capturing the image. In addition, the local
drive could be removed from the system prior to the first boot from the FCoE LUN.
Содержание 10 Gigabit AT Ethernet Server Adapter
Страница 1: ...Intel Ethernet Adapters and Devices User Guide ...
Страница 107: ...FCoE Target Selection Menu ...