Users Guide

6–Boot from SAN Configuration
FCoE Boot from SAN
122 AH0054602-00 M
Injecting (Slipstreaming) Adapter Drivers into Windows Image Files
To inject adapter drivers into the Windows image files:
1. Obtain the latest driver package for the applicable Windows Server version
(2012, 2012 R2, 2016, or 2019).
2. Extract the driver package to a working directory:
a. Open a command line session and navigate to the folder that contains
the driver package.
b. To extract the driver Dell Update Package (DUP), issue the following
command:
start /wait NameOfDup.exe /s /drivers=<folder path>
3. Download the Windows Assessment and Deployment Kit (ADK) version 10
from Microsoft:
https://developer.microsoft.com/en-us/windows/hardware/
windows-assessment-deployment-kit
4. Follow the Microsoft “Add and Remove Drivers to an offline Windows Image
article” and inject the OOB driver extracted on Step 2, part b. See
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/a
dd-and-remove-drivers-to-an-offline-windows-image
Configuring FCoE Boot from SAN on Linux
FCoE boot from SAN configuration for Linux covers the following:
 Prerequisites for Linux FCoE Boot from SAN
 Configuring Linux FCoE Boot from SAN
Prerequisites for Linux FCoE Boot from SAN
The following are required for Linux FCoE boot from SAN to function correctly with
the Marvell FastLinQ 41xxx 10/25GbE Controller.
General
You no longer need to use the FCoE disk tabs in the Red Hat and SUSE installers
because the FCoE interfaces are not exposed from the network interface and are
automatically activated by the qedf driver.
SLES 12 and SLES 15
 Driver update disk is recommended for SLES 12 SP 3 and later.
 The installer parameter
dud=1 is required to ensure that the installer will
ask for the driver update disk.