Skip Navigation Links | |
Exit Print View | |
![]() |
Sun Dual 10GbE PCIe 2.0 Fibre Channel Over Ethernet Product Notes |
1. Important Information About FCoE
Intel 10-GbE Driver Support for Linux and Windows
Adding or Removing an Adapter as a VNIC Does Not Load the Storage Miniport Driver
Installing the FCoE Image After Installing ANS and Creating AFT Teams Does Not Install Storports
Link Aggregation Teams Are Not Supported
Using the FCoE CTRL-D Utility Is Not Possible With the Windows Device Manager
Displaying 82599-Based Adapter Is Not Possible in Windows MPIO Configurations
Removing ALB Teaming Causes All FCoE Functions to Fail
Ethernet Virtual Storage Miniport Driver Disappears From the Device Manager
Boot-Option ROM and Windows Boot Issues
Discovering the Desired VLAN Might Fail
Having an Installed Local Disk Causes FCoE to Fail in Windows OS
Stopping the IntelDCB Service Might Cause the OS to Hang or Crash
Uninstalling FCoE From a Local Disk Might Be Blocked
Creating VLAN Interfaces Fails With the FCoE Boot Option Enabled
Configuring an Adapter Port as the FCoE Boot Option Displays the Port as an Externally Shared VNIC
Setting the FCoE Linkdown Timeout Value Fails Prematurely When the System Is Booted Remotely
The FCoE Boot option ROM might 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.
The Windows OS uses a paging file on the local disk. After imaging, if the local disk is not removed before booting from the FCoE disk, then the Windows OS might use the paging file from the local disk.
Crash dump to FCoE disks is supported only to the FCoE Boot LUN.
The following scenarios are not supported:
Crash dump to an FCoE disk if the Windows OS directory is not on the FCoE Boot LUN.
Use of the DedicatedDumpFile registry value to direct crash dump to another FCoE LUN.
Do not stop the IntelDCB service.
Uninstalling FCoE from a local disk might be blocked because the installer inaccurately reports that the system is booted from FCoE. When the FCoE Boot option ROM connects to an FCoE disk during the boot process, the Windows installer might be unable to determine if the system was booted from FCoE or not, so the installer might block the FCoE uninstall.
Workaround: To uninstall, configure the FCoE Boot option ROM so that it does not connect to an FCoE disk.
If you boot the system with FCoE, you cannot create VLANs or teams for other traffic types. This situation prevents converged functionality for non-FCoE traffic.
If you set a port as a boot port, install the Hyper-V role in the system, and then go into the Hyper-V Network Manager to select which port to virtualize externally, the boot port displays, which it should not.
When setting the port to a boot port in the Windows Device Manager, a displayed message states that you should restart the system for the changes to take effect, but the Windows Device Manager does not force a restart. As a result, the user level applications appear to be in the boot mode (that is, the Data Center Tab is grayed out), but the kernel level drivers have not been restarted to indicate to the OS that the port is a boot port. If you then add the Hyper-V service to the system, the OS takes a snap shot of the available ports, and this snap shot is used when the Hyper‐V role is added. Thus, when you restart the system and go into the Hyper-V Virtual Network Manager to virtualize the ports, the boot port is also displayed.
Workarounds: If this issue occurs, try one of the following:
Restart the system after you set the port to a boot port and before you add the Hyper-V role. The port should not appear in the list of virtualizable ports in the Hyper-V Virtual Network Manager.
Disable or enable the port in the Windows Device Manager after you set the port to the boot port and before you add the Hyper-V role. The port should not appear in the list of virtualizable ports in the Hyper-V Virtual Network Manager.
If an FCoE-booted port loses its link for longer than the time specified in the linkdown timeout advanced setting in the Intel Ethernet Virtual Storage Miniport Driver, the system will crash. Linkdown timeout values greater than 30 seconds might not provide extra time before a system crash.