DescriptionName
Thiscan be one of the following:
Primary—Thefirst address defined for the
associatedboot device class. A boot policy can
onlyhave one primaryLAN, SAN, oriSCSI
bootlocation.
Secondary—Thesecond address defined for
theassociated boot deviceclass. Each boot
policycan have only one secondary LAN or
SANboot location.
Theuse of the terms primary or secondary boot
devicesdoes not imply a boot order. The effective
orderof boot devices within the same device class is
determinedby PCIe busscan order.
Typefield
Step 5 Doone ofthe following:
• Add another boot device to the Boot Order table.
• Click OK to finish.
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.
iSCSI Boot
iSCSIboot enables a server to boot its operating system from an iSCSI target machine located remotely over
anetwork.
iSCSIboot is supportedon thefollowing Cisco UCS hardware:
• Cisco UCS server blades that have the Cisco UCS M51KR-B Broadcom BCM57711network adapter
anduse thedefault MAC address providedby Broadcom.
• Cisco UCS M81KR VirtualInterface Card
• Cisco UCS M82-8P VirtualInterface Card
Thereare prerequisites that must be met before you configure iSCSI boot. For a list of these prerequisites,
seeiSCSI BootGuidelines and Prerequisites, on page 444.
Fora high-levelprocedure for implementingiSCSI boot, seeConfiguring iSCSI Boot, on page 446.
Cisco UCS Manager GUI Configuration Guide, Release 2.0
OL-25712-04 443
iSCSI Boot