DescriptionName
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
d) 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
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
e) Add another boot device to the Boot Order table, or click OK to finish.
Step 14
Click OK.
Cisco UCS Manager GUI Configuration Guide, Release 2.0
552 OL-25712-04
Managing Service Profiles