System information

/> tcm_fc/ create 00:11:22:33:44:55:66:77
If FCoE interfaces are present on the system, tab-completing after create will list available
interfaces. If not, ensure fco ead m -i shows active interfaces.
6. Map a backstore to the target instance.
Examp le 25.7. Examp le of map p in g a backst o re t o t h e t arg et in st an ce
/> cd tcm_fc/00:11:22:33:44:55:66:77
/> l uns/ create /backsto res/fi l ei o /example2
7. Allow access to the LUN from an FCoE initiator.
/> acl s/ create 00:99:88:77:66:55:44:33
The LUN should now be accessible to that initiator.
8. Exit targ etcl i by typing exi t or entering ctrl +D .
Exiting targ etcl i will save the configuration by default. However it may be explicitly saved with the
saveco nfi g command.
Refer to the targ etcl i manpage for more information.
25.8. Configuring an FCoE Int erface t o Aut omat ically Mount at Boot
Note
The instructions in this section are available in /usr/share/d o c/fco e-
uti l s-version/R EAD ME as of Red Hat Enterprise Linux 6.1. Refer to that document for any
possible changes throughout minor releases.
You can mount newly discovered disks via ud ev rules, auto fs, 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 fco e 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 fco e service. The fco e startup script is /etc/i ni t. d /fco e.
The FCoE mounting code is different per system configuration, whether you are using a simple
formatted FCoE disk, LVM, or multipathed device node.
Examp le 25.8. FCoE mo u n t in g co d e
The following is a sample FCoE mounting code for mounting file systems specified via wild cards
in /etc/fstab:
⁠Chapt er 2 5. O nline St orag e Manag ement
179