Installation guide

Chapter 21. Online Storage Management
130
ifconfig ethX up
6. Start FCoE using:
/etc/init.d/fcoe start
The FCoE device should appear shortly, assuming all other settings on the fabric are correct. To
view configured FCoE devices, run:
fcoeadmin -i
After correctly configuring the ethernet interface to use FCoE, Red Hat recommends that you set
FCoE and lldpad to run at startup. To do so, use chkconfig, as in:
chkconfig lldpad on
chkconfig fcoe on
Warning
Do not run software-based DCB or LLDP on CNAs that implement DCB.
Some Combined Network Adapters (CNAs) implement the Data Center Bridging (DCB) protocol
in firmware. The DCB protocol assumes that there is just one originator of DCB on a particular
network link. This means that any higher-level software implementation of DCB, or Link Layer
Discovery Protocol (LLDP), must be disabled on CNAs that implement DCB.
21.8. Configuring an FCoE Interface to Automatically Mount
at Boot
Note
The instructions in this section are available in /usr/share/doc/fcoe-utils-version/
README as of Red Hat Enterprise Linux 6.1. Please refer to that document for any possible
changes throughout minor releases.
You can mount newly discovered disks via udev rules, autofs, and other similar methods.
Sometimes, however, a specific service might require the FCoE disk to be mounted at boot-time.
In such cases, the FCoE disk should be mounted as soon as the fcoe service runs and before the
initiation of any service that requires the FCoE disk.
To configure an FCoE disk to automatically mount at boot, add proper FCoE mounting code to the
startup script for the fcoe service. The fcoe startup script is /etc/init.d/fcoe.
The FCoE mounting code is different per system configuration, whether you are using a simple
formatted FCoE disk, LVM, or multipathed device node. The following is a sample FCoE mounting
code for mounting file systems specified via wild cards in /etc/fstab:
mount_fcoe_disks_from_fstab()
{
local timeout=20
local done=1