10.01.2013 Views

SAN Boot Implementation and Best Practices Guide ... - IBM Redbooks

SAN Boot Implementation and Best Practices Guide ... - IBM Redbooks

SAN Boot Implementation and Best Practices Guide ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Tip: Note the name of the new mpp initrd image that is created in your /boot directory.<br />

In this example, the name is mpp-2.6.18-194.el5.img.<br />

6. Open the /boot/grub/menu.lst file with your preferred text editor.<br />

7. Create a new boot entry by copying the first boot entry. Then edit the initrd line to point to<br />

the new initrd file so that the mpp initrd is booted. The new initrd line should look similar to<br />

Example 2-7.<br />

Make sure that the default is set to boot to the entry you just created (default=0 means the<br />

system is default to boot to the first boot entry). You need to change the (hd0,0), <strong>and</strong> the<br />

root to be the same as what is in your menu.lst.<br />

Example 2-7 Changes to the menu.lst<br />

default=0<br />

timeout=5<br />

splashimge=(hd0,0)/boot/grub/splash.xpm.gz<br />

hiddenmenu<br />

title Red Hat Enterprise Linux Server with mpp support (2.6.18-194.el5)<br />

root (hd0,0)<br />

kernel /boot/vmlinuz-2.6.18-194.el5 ro root=/dev/VolGroup00/LogVol00 rhgb<br />

quiet<br />

initrd/boot/mpp-2.6.18-194.el5.img<br />

title Red Hat Enterprise Linux Server (2.6.18-194.el5)<br />

root (hd0,0)<br />

kernel /boot/vmlinuz-2.6.18-194.el5 ro root=/dev/VolGroup00/LogVol00 rhgb<br />

quiet<br />

initrd/boot/initrd-2.6.18-194.el5.img<br />

8. Reboot the system.<br />

9. When the system is back up, verify that the mpp driver is installed correctly by running the<br />

following comm<strong>and</strong> from the comm<strong>and</strong> line (Example 2-8).<br />

Example 2-8 Verify the mpp driver<br />

ls -lR /proc/mpp/<br />

10.You should see that all the physical LUNs have been discovered <strong>and</strong> that the virtual LUNs<br />

have been created. For this example, because the environment has three physical LUNs,<br />

running ls -lR /proc/mpp/ produced three virtual LUNs: virtualLun0.<br />

ls -1R /proc/mpp also shows us that controller A is connected to one physical LUN:<br />

LUN0 (see Example 2-114).<br />

94 <strong>SAN</strong> <strong>Boot</strong> <strong>Implementation</strong> <strong>and</strong> <strong>Best</strong> <strong>Practices</strong> <strong>Guide</strong> for <strong>IBM</strong> System Storage

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!