Fibre Channel Over Ethernet: Broadcom NetXtreme II Network Adapter User Guide
file:///T|/htdocs/NETWORK/BroadCom/71921/NetXtremeII/en/fcoe.htm[9/26/2012 3:29:33 PM]
11. Now that the local drive is reconfigured to support FCoE boot. Copy the entire local hard drive contents to the SAN LUN
via dd:
# dd if=<SOURCE> of=<DEST> bs=1MB
where <SOURCE> is the local disk (e.g. /dev/sda)
and <DEST> is the SAN LUN (e.g. /dev/sdc)
12. Restore '/boot/grub/menu.lst' and '/etc/fstab' files to their original contents by copying the backup files created above
to their original filenames.
RHEL6.0 Installation
1. Install RHEL 6.0 to a locally attached hard drive.
2. Use
Vol-Group
option during installation (default).
3. Once installation is complete, install the Broadcom linux-nx2 driver package and ensure a connection to the desired
SAN boot LUN.
4. For multipathd/device-mapper configurations, enable multipath services by using the following commands:
# chkconfig --level 0123456 multipathd on
5. Set network services to start at all run levels:
# chkconfig --level 0123456 network on
or
# chkconfig --level 0123456 NetworkManager on
6. Run fcoe_setup.sh to create FCoE INITRD and copy the created INITRD file to /boot:
# ./fcoe_setup.sh
# cp fcoe-initrd.img /boot
7. Create backups of '/boot/grub/menu.lst'
8. Add a new boot entry to /boot/grub/menu.lst by pointing INITRD to the new INITRD that was created in step 7,
/boot/fcoe-initrd.img.
9. Now that the local drive is reconfigured to support FCoE boot. Copy the entire local hard drive contents to the SAN LUN
via dd:
# dd if=<SOURCE> of=<DEST> bs=1MB
where <SOURCE> is the local disk (e.g. /dev/sda)
and <DEST> is the SAN LUN (e.g. /dev/sdc)
10. Because the LVM drive drive/group/volume signatures are now identical between the local HDD and the SAN LUN, the
local HDD must be removed prior to reboot and booting from SAN in order to prevent LVM discovery conflicts.
11. Restore '/boot/grub/menu.lst' its original contents by copying the backup files created above to their original filenames.
Booting from SAN After Installation
Now that boot configuration and OS installation are complete, you can reboot and test the installation. On this and all future
reboots, no other user interactivity is required. Ignore the
CTRL+D
prompt and allow the system to boot through to the FCoE
SAN LUN.
At this time, if additional redundant failover paths are desired, you can configure those paths through CCM, and the MBA will
automatically failover to secondary paths if the first path is not available. Further, the redundant boot paths will yield
redundant paths visible through host MPIO software allowing for a fault tolerant configuration.