User guide

User Guide NetXtreme II
September 2013
Broadcom Corporation
Document INGSRVT78-CDUM100-R FCoE Boot from SAN Page 219
3. Create a /etc/fcoe/cfg-<INTERFACE> file for each new FCoE initiator by duplicating the /etc/fcoe/cfg-
<INTERFACE> file that was already configured during initial installation.
4. Execute nm-connection-editor.
a. Open Network Connection and choose each new interface.
b. Configure each interface as desired, including DHCP settings.
c. Click Apply to save.
5. For each new interface, edit /etc/sysconfig/network-scripts/ifcfg-<INTERFACE> to add the line
NM_CONTROLLED="no". Modifying these files automatically causes a restart to the network service. This may cause the
system to appear to hang briefly. It is best to ensure that redundant multipath paths are available before performing this
operation.
SLES 11 SP2 and Above
On SLES11 SP2, if the system boots through an initiator that has not been configured as an FCoE interface during
installation, the system will fail to boot. To add new boot paths, the system must boot up through the configured FCoE
interface.
1. Configure a new FCoE interface that will be added as a new path so it can discover the boot LUN.
a. Create a /etc/fcoe/cfg-<INTERFACE> file for each new FCoE initiator by duplicating the /etc/fcoe/cfg-
<INTERFACE> file that was already configured during initial installation.
b. Bring up the new interfaces:
# ifconfig <INTERFACE> up
c. Restart FCoE service:
# rcfcoe restart
2. Run multipath -l to make sure the system has a correct number of multipaths to the boot LUN, including new paths.
3. Create a /etc/sysconfig/network/ifcfg-<INTERFACE> file for each new interface by duplicating the /etc/
sysconfig/network/ifcfg-<INTERFACE> file that was already configured during initial installation.
4. Create a new ramdisk to update changes:
# mkinitrd