8–FCoE Configuration
Boot from SAN Considerations
122
AH0054602-00 A
3.
Check for discovered FCoE devices using
lsblk -S
:
#
lsblk -S
NAME HCTL
TYPE
VENDOR
MODEL
REV TRAN
sdb 5:0:0:0 disk SANBlaze VLUN P2T1L0 V7.3 fc
sdc 5:0:0:1 disk SANBlaze VLUN P2T1L1 V7.3 fc
sdd 5:0:0:2 disk SANBlaze VLUN P2T1L2 V7.3 fc
sde 5:0:0:3 disk SANBlaze VLUN P2T1L3 V7.3 fc
sdf 5:0:0:4 disk SANBlaze VLUN P2T1L4 V7.3 fc
sdg 5:0:0:5 disk SANBlaze VLUN P2T1L5 V7.3 fc
sdh 5:0:0:6 disk SANBlaze VLUN P2T1L6 V7.3 fc
sdi 5:0:0:7 disk SANBlaze VLUN P2T1L7 V7.3 fc
sdj 5:0:0:8 disk SANBlaze VLUN P2T1L8 V7.3 fc
sdk 5:0:0:9 disk SANBlaze VLUN P2T1L9 V7.3 fc
Configuration information for the host is located in
/sys/class/fc_host/host
X
,
where
X
is the number of the SCSI host. In
the preceding example,
X
could 4 or 5. The
host
X
file contains attributes for
the FCoE function, such as worldwide port name and fabric ID.
Boot from SAN Considerations
FCoE boot from SAN should work like FC boot from SAN, where the module
simply needs to be injected by the driver update disk (DUD) into the installation
environment. The disks from any remote targets are discovered automatically.
Installation can then proceed as if the remote disks are local disks.
