User guide

NetXtreme II User Guide
September 2013
Broadcom Corporation
Page 224 Booting from SAN After Installation Document INGSRVT78-CDUM100-R
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.
DRIVER UPGRADE ON LINUX BOOT FROM SAN SYSTEMS
1. Remove the existing installed NetXtreme ll package. Log in as root. Query for the existing NetXtreme ll package and
remove it using the following commands:
# rpm -e <NetXtreme II package name>
For example:
rpm -e netxtreme2
or:
rpm -e netxtreme2-x.y.z-1.x86_64
2. Install the binary RPM containing the new driver version. Refer to the linux-nx2 package README for instructions on
how to prepare a binary driver RPM.
3. Use the following command to update the ramdisk:
• On RHEL 6.x systems, execute: dracut -force
• On SLES11spX systems, execute: mkinitrd
4. If you are using different name for the initrd under /boot, be sure to overwrite it with the default, as dracut/mkinitrd updates