Filter
Top Products
Creating a Boot Policy
You can also create a local boot policy that is restricted to a service profile or service profile template. However,
except for iSCSI boot, we recommend that you create a global boot policy that can be included in multiple
service profiles or service profile templates.
Procedure
Step 1
In the Navigation pane, click the Servers tab.
Step 2
On the Servers tab, expand Servers > Policies.
Step 3
Expand the node for the organization where you want to create the policy.
If the system does not include multitenancy, expand the root node.
Step 4
Right-click Boot Policies and select Create Boot Policy.
The Create Boot Policy wizard displays.
Step 5
Enter a unique name and description for the policy.
This name can be between 1 and 16 alphanumeric characters. You cannot use spaces or any special characters
other than - (hyphen), _ (underscore), : (colon), and . (period), and you cannot change this name after the
object has been saved.
Step 6
(Optional) To reboot all servers that use this boot policy after you make changes to the boot order, check the
Reboot on Boot Order Change check box.
In the Cisco UCS Manager GUI, if the Reboot on Boot Order Change check box is checked for a boot
policy, and if CD-ROM or Floppy is the last device in the boot order, deleting or adding the device does not
directly affect the boot order and the server does not reboot.
Step 7
(Optional) If desired, check the Enforce vNIC/vHBA/iSCSI Name check box.
• If checked, 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 match the server configuration in the
service profile.
• If not checked, Cisco UCS Manager uses the vNICs, vHBAs, or iSCSI vNICs (as appropriate for the
boot option) from the server 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
Configure one or more of the following boot options for the boot policy and set their boot order:
• SAN Boot—To boot from an operating system image on the SAN, continue with Configuring a SAN
Boot for a Boot Policy, on page 441.
You can specify a primary and a secondary SAN boot. If the primary boot fails, the server attempts to
boot from the secondary.
• iSCSI Boot—To boot from an iSCSI LUN, continue with Creating an iSCSI Boot Policy, on page 451.
• LAN Boot—To boot from a centralized provisioning server, continue with Configuring a LAN Boot
for a Boot Policy, on page 465.
• Local Disk boot—To boot from the local disk on the server, continue with Configuring a Local Disk
Boot for a Boot Policy, on page 466.
Cisco UCS Manager GUI Configuration Guide, Release 2.0
440 OL-25712-04
Creating a Boot Policy