Red Hat Enterprise Linux - Intel XL710-Q2 User Manual

Red Hat Enterprise Linux

For the easiest experience installing Linux onto an iSCSI target, you should use RHEL 6 or greater. RHEL 6
provides native support for iSCSI Booting and installing. This means that there are no additional steps outside
of the installer that are necessary to install to an iSCSI target using an Intel Ethernet Server Adapter. Please
refer to the RHEL 6 documentation for instructions on how to install to an iSCSI LUN.
FCoE Known Issues
Intel® Ethernet FCoE Windows Issues
Intel® Ethernet Virtual Storage Miniport Driver for FCoE may disappear from Device Manager
The Intel® Ethernet Virtual Storage Miniport Driver for FCoE may disappear from the Device Manager after
either:
A virtual network is removed.
l
The underlying Intel NIC adapter settings are modified.
l
This can occur when the corresponding Intel adapter is virtualized to create a new virtual network or delete or
modify an existing Virtual Network. It can also happen when the underlying Intel NIC adapter settings are
modified, including disabling or re-enabling the adapter.
As a workaround, remove all the resource dependencies of the Intel® Ethernet Virtual Storage Miniport Driver
for FCoE that are currently being used by the system before making any changes to the Intel adapter for
virtualization. For example, in one use case scenario, the user may have assigned the FCoE disk(s) from the
FCoE storage driver to run one of its Virtual Machines, and at the same time the user wants to alter the
configuration of the same Intel adapter for virtualization. In this scenario the user must remove the FCoE
disks(s) from the Virtual Machine before altering the Intel adapter configuration.
Virtual Port may disappear from Virtual Machine
When the Virtual Machine starts, it asks the Intel® Ethernet Virtual Storage Miniport Driver for FCoE ("the
driver") to create a Virtual Port. If the driver is subsequently disabled, the Virtual Port may disappear. The only
way to get the Virtual Port back is to enable the driver and reboot the Virtual Machine.
When installing FCoE after installing ANS and creating AFT Team, Storports are not installed
If the user installs ANS and creates an AFT team and then installs FCoE/DCB, the result is that DCB is off by
default. If the user then enables DCB on one port, the OS detects Storports and the user must manually click
on the new hardware wizard prompts for each of them to install. If the user does not do that, DCB status is
non-operational and the reason given is no peer.
Intel® PROSet for Windows Device Manager (DMiX) is not synched with FCoE CTRL-D Utility
When the user disables FCoE via the Control-D menu, the Intel PROSet for Windows Device Manager User
Interface states that the flash contains an FCoE image, but that the flash needs to be updated. Updating the
flash with the FCoE image again, re-enables FCoE and returns the user to the state where all the FCoE
settings are available.
If the user uses the control-D menu to disable FCoE, then they should use the control-D menu to enable it
because Intel PROSet for Windows Device Manager does not support enabling or disabling FCoE.
82599 and X540-based adapters don't display as SPC-3 compliant in Windows MPIO configuration
Because the FCoE initiator is a virtualized device it does not have its own unique hardware ID and thus is not
displayed as a SPC-3 compliant device in Windows MPIO configuration.