Users Guide

13–Fibre Channel Over Ethernet
FCoE Boot from SAN
213 BC0054508-00 M
 Data center bridging (DCB) provides lossless behavior with priority flow
control (PFC)
 DCB allocates a share of link bandwidth to FCoE traffic with enhanced
transmission selection (ETS)
DCB supports storage, management, computing, and communications fabrics
onto a single physical fabric that is simpler to deploy, upgrade, and maintain than
in standard Ethernet networks. DCB technology allows the capable Marvell
C-NICs to provide lossless data delivery, lower latency, and standards-based
bandwidth sharing of data center physical links. The DCB supports FCoE, iSCSI,
network attached storage (NAS), management, and IPC traffic flows. For more
information on DCB, see Chapter 14 Data Center Bridging.
Configure NPIV in Windows QCC GUI by clicking an FCoE adapter instance and
then selecting either Create a Virtual Port or Create Multiple Virtual Ports. You
can also issue the QCS CLI createnpivport and createmultinpivport
commands. Configure NPIV in Linux by issuing the vport_create command.
Add Windows Server 2012 R2 vFCs by using the Hyper-V Virtual SAN Manager
or by issuing the Windows Server 2012 R2 (and later) PowerShell
Add-VMFibreChannelHBA command.
FCoE Boot from SAN
This section describes the install and boot procedures for the Windows, Linux,
and ESXi operating systems.
The following section details the BIOS setup and configuration of the boot
environment prior to the OS install.
Preparing System BIOS for FCoE Build and Boot
To prepare the system BIOS for the FCoE build and boot, modify the system boot
order and specify the BIOS boot protocol, if required.
Modifying System Boot Order
The Marvell initiator must be the first entry in the system boot order. The second
entry must be the OS installation media. It is important that you correctly set the
boot order, otherwise the installation will not proceed correctly. Either the boot
LUN that you want will not be discovered, or it will be discovered but marked
offline.
Specifying BIOS Boot Protocol (If Required)
On some platforms, the boot protocol must be configured through system BIOS
configuration. On all other systems the boot protocol is specified through the
Marvell Comprehensive Configuration Management (CCM), and for those
systems this step is not required.