DescriptionName
Thiscan be one of the following:
•Primary—Thefirst address defined for the
associatedboot device class. A boot policy
canonly have one primaryLAN, SAN, or
iSCSIboot location.
•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 bootdevices within thesame device class
isdetermined by PCIebus scanorder.
Typefield
e) Add another boot device to the Boot Order table, or click OK to finish.
Step 8 Toadd an iSCSI boot to the boot order, do the following:
a) In the Specific Boot Policy area, click the down arrows to expand the iSCSI vNICs area.
b) In the iSCSI vNICs area, double-click the iSCSI vNICs from which you want to boot the server to add
themto the Boot Ordertable.
c) In the iSCSI vNICs area, click the Set Boot Parameters link.
Ifthere are two iSCSIvNICs, choose the one for whichyou wantto setboot parameters.
d) Complete the fields in the Set iSCSI Boot Parameters dialog box and then click OK.
Formore information about the fields, see Setting iSCSI Boot Parameters, on page 454.
e) Repeat steps c and d to set boot parameters for additional iSCSI vNICs.
Step 9 Ifyou createda new bootpolicy accessible to all service profiles and template, choose that policy from the
BootPolicy drop-down list.
Step 10 Click Next.
What to Do Next
CompletePage 6: Addingthe MaintenancePolicy, on page 535.
Page 6: Adding the Maintenance Policy
Thisprocedure directly follows Page 5: Setting the Server BootOrder, on page 532. It describes how to add
amaintenance policy to the service profile on the Maintenance Policy page of the Create Service Profile
(expert)wizard.
Cisco UCS Manager GUI Configuration Guide, Release 2.0
OL-25712-04 535
Working with Service Profile Templates