Creating 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, werecommend that you create a global boot policythat can be includedin multiple
serviceprofiles or serviceprofile templates.
Procedure
Step 1 Inthe Navigation pane, clickthe Servers tab.
Step 2 Onthe Servers tab, expand Servers >Policies.
Step 3 Expandthe node for theorganization where you want to create the policy.
Ifthe system does not includemultitenancy, expand the root node.
Step 4 Right-clickBoot Policies and selectCreate Boot Policy.
TheCreate Boot Policy wizard displays.
Step 5 Entera unique name and description for the policy.
Thisname can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters
otherthan - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the
objecthas been saved.
Step 6 (Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the
Rebooton BootOrder Change checkbox.
Inthe Cisco UCS Manager GUI, if theReboot onBoot OrderChange check box ischecked for aboot
policy,and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not
directlyaffect the boot order and the server does not reboot.
Step 7 (Optional) If desired,check the Enforce vNIC/vHBA/iSCSI Name check box.
•Ifchecked, Cisco UCS Manager displays a configuration error and reports whether one or more of the
vNICs,vHBAs, or iSCSI vNICs listed in the Boot Order table matchthe server configuration in the
serviceprofile.
•Ifnot checked,Cisco UCS Manager uses the vNICs, vHBAs, or iSCSI vNICs (as appropriate for the
bootoption) from theserver configuration in the service profile. It does not report whether the vNICs,
vHBAs,or iSCSI vNICs specified in the boot policy match the server configuration in the service profile.
Step 8 Configureone or more of the following boot options for the boot policy and set their boot order:
•SANBoot—To boot from an operating system image on the SAN, continue with Configuring a SAN
Bootfor a BootPolicy, on page 441.
Youcan specify a primary and a secondary SAN boot. If the primary boot fails, the server attempts to
bootfrom thesecondary.
•iSCSIBoot—To boot from an iSCSI LUN, continue with Creating an iSCSI Boot Policy, on page 451.
•LANBoot—To boot from a centralized provisioning server, continue with Configuring a LAN Boot
fora BootPolicy, on page 465.
•LocalDisk boot—To boot from the local disk on the server, continue with Configuring a Local Disk
Bootfor a BootPolicy, on page 466.
Cisco UCS Manager GUI Configuration Guide, Release 2.0
440 OL-25712-04
Creating a Boot Policy