Intel XL710-Q2 User Manual page 116

When removing ALB teaming, all FCOE functions fail, all DMIX tabs are grayed out, and both adapter ports fail
For ANS teaming to work with Microsoft Network Load Balancer (NLB) in unicast mode, the team's LAA must
be set to cluster node IP. For ALB mode, Receive Load Balancing must be disabled. For further configuration
details, refer to http://support.microsoft.com/?id=278431
ANS teaming will work when NLB is in multicast mode, as well. For proper configuration of the adapter in this
mode, refer to http://technet.microsoft.com/en-ca/library/cc726473(WS.10).aspx
FCoE and TCP/IP traffic on the same VLAN may not work on some switches
This is a known switch design and configuration issue.
Intel® Ethernet 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:
Crash dump to an FCoE disk if the Windows directory is not on the FCoE Boot LUN.
l
Use of the DedicatedDumpFile registry value to direct crash dump to another FCoE LUN.
l
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 (i.e., Data Center Tab is grayed out) but kernel level drivers haven't been
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 and this is the snap shot that it uses after the Hyper V
role is added, 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.