Users Guide

6–Boot from SAN Configuration
iSCSI Boot from SAN
97 AH0054602-00 M
Configuring iSCSI Boot from SAN for SLES 12 SP3 and Later
To install SLES 12 SP3 and later:
1. Boot from the SLES 12 SP3 installation media with the iSCSI target
pre-configured and connected in UEFI.
2. Update the latest driver package by adding the
dud=1 parameter in the
installer command parameter. The driver update disk is required because
the necessary iSCSI drivers are not inbox.
3. Complete the installation steps specified by the SLES 12 SP3 OS.
Known Issue in DHCP Configuration
In DHCP configuration for SLES 12 SP3 and later, the first boot after an OS
installation may fail if the initiator IP address acquired from the DHCP server is in
a different range than the target IP address. To resolve this issue, boot the OS
using static configuration, update the latest iscsiuio out-of-box RPM, rebuild the
initrd, and then reboot the OS using DHCP configuration. The OS should now
boot successfully.
Configuring iSCSI Boot from SAN for Other Linux Distributions
For distributions such as RHEL 6.9/6.10/7.2/7.3, SLES 11 SP4, and SLES 12
SP1/2, the inbox iSCSI user space utility (Open-iSCSI tools) lacks support for qedi
iSCSI transport and cannot perform user space-initiated iSCSI functionality.
During boot from SAN installation, you can update the qedi driver using a driver
update disk (DUD). However, no interface or process exists to update userspace
inbox utilities, which causes the iSCSI target login and boot from SAN installation
to fail.
To overcome this limitation, perform the initial boot from SAN with the pure L2
interface (do not use hardware-offloaded iSCSI) using the following procedure
during the boot from SAN.
NOTE
For SLES 12 SP3 only: If the server is configured for Multi-Function
mode (NPAR), you must provide the following additional parameters
as part of this step:
dud=1 brokenmodules=qed,qedi,qedf,qede withiscsi=1
[BOOT_IMAGE=/boot/x86_64/loader/linux dud=1
brokenmodules=qed,qedi,qedf,qede withiscsi=1]