Linux issues – Dell Intel PRO Family of Adapters User Manual
Page 49
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. This is the snap shot that it uses after the Hyper V role is added, the
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.
FCoE Linkdown Timeout fails prematurely when remote booted
If and FCoE-booted port loses link for longer than the time specified in the Linkdown Timeout advanced setting in Intel®
Ethernet Virtual Storage Miniport Driver, 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 the Windows Disk Management tool. If the drive letters differ, the
Windows installation is split between the two disks.
If this occurs, ensure that fcoeprep is run prior to capturing the image and that the system is not allowed to boot
locally 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.
For detailed instructions on installing using the imaging method, see
Installing Windows Server with Local Disk
.
Linux Issues
Intermittent Failure to Remote Boot with X540 Adapter on SLES 11 SP3
Remote boot with SuSE11 SP3 and a x540 adapter can intermittently fail to complete. This is due to a timing issue involving
DCB in some hardware configurations.
.
.