•VirtualMedia Boot —To boot from virtual media that mimics the insertion of a physical CD or floppy
driveinto aserver, continue with Configuring a Virtual Media Boot for a Boot Policy, on page 466.
What to Do Next
Includethe boot policy in a service profile and/or template.
Aftera server is associated with a service profile that includes this boot policy, you can verify the actual boot
orderin the Boot OrderDetails area on the Generaltab for the server.
SAN Boot
Youcan configure a boot policy to boot one or more servers from an operating system image on the SAN.
Theboot policy can include a primary and a secondary SAN boot. If the primary boot fails, the server attempts
toboot from the secondary.
Werecommend that you use a SAN boot, because it offers the most service profile mobility within the system.
Ifyou boot from the SAN when you move a service profile from one server to another, the new server boots
fromthe exact same operating system image. Therefore, the new server appears to be the exact same server
tothe network.
Touse a SAN boot, ensure that the following is configured:
•TheCisco UCS domain must be able to communicate with the SAN storage device that hosts the operating
systemimage.
• A boot targetLUN on the device where the operatingsystem image is located.

Configuring a SAN Boot for a Boot Policy

Youcan also create a local boot policy that is restricted to a service profile or service profile template. However,
exceptfor iSCSI boot, we recommendthat you createa globalboot policythat can be includedin multiple
serviceprofiles or serviceprofile templates.
Werecommend that the boot order in a boot policy include either a local disk or a SAN LUN, but not
both,to avoid the possibilityof the server booting from the wrong storage type. If you configure a local
diskand a SAN LUN for the boot order storage type and the operating system or logical volume manager
(LVM)is configured incorrectly, the server might boot from the local disk rather than the SAN LUN.
Forexample, on a serverwith Red Hat Linux installed,where the LVM is configured with default LV
namesand the boot order is configured with a SAN LUN and a local disk, Linux reports that there are
twoLVs with the same name and boots from the LV with the lowest SCSI ID, which could be the local
disk.
Tip
Thisprocedure continues directlyfrom Creating a BootPolicy, onpage 440.
Cisco UCS Manager GUI Configuration Guide, Release 2.0
OL-25712-04 441
SAN Boot