Before You Begin
If you are creating a boot policy that boots the server from a SAN LUN and you require reliable SAN
boot operations, we recommend that you first remove all local disks from servers associated with a service
profile that includes the boot policy.
Note
Procedure
Step 1
Click the down arrows to expand the vHBAs area.
Step 2
Click the Add SAN Boot link.
Step 3
In the Add SAN Boot dialog box, complete the following fields, and click OK:
DescriptionName
Enter the name of the vHBA you want to use for the SAN boot.vHBA field
This can be one of the following:
• Primary—The first address defined for the associated boot device
class. A boot policy can only have one primary LAN, SAN, or
iSCSI boot location.
• Secondary—The second address defined for the associated boot
device class. Each boot policy can have only one secondary LAN
or SAN boot location.
The use of the terms primary or secondary boot devices does not imply
a boot order. The effective order of boot devices within the same device
class is determined by PCIe bus scan order.
Type field
Step 4
If this vHBA points to a bootable SAN image, click the Add SAN Boot Target link and, in the Add SAN
Boot Target dialog box, complete the following fields, then click OK:
DescriptionName
The LUN that corresponds to the location of the boot
image.
Boot Target LUN field
The WWPN that corresponds to the location of the
boot image.
Boot Target WWPN field
Cisco UCS Manager GUI Configuration Guide, Release 2.0
442 OL-25712-04
SAN Boot