A Boot Order Policy defines the sequence in which devices are attempted during server startup. It supports UEFI and Legacy boot modes and a wide range of device types including PXE, local disk, SAN, HTTP boot, and virtual media. The policy is applied to servers via a Server Profile Template.
Note: Intersight does not allow a boot order policy with an HTTP boot device that has a static IP address (ip_config_type: Static) on a server template, only on a server profile. Use DHCP for a policy that a server template references, or set the policy for each server in servers[].provisioning.intersight.policies.boot_order_policy. Validation reports a server template that references such a policy.
Example-1: The example below demonstrates a UEFI policy that first attempts PXE boot on a named interface, then falls back to a local disk with a specified UEFI bootloader path.
compute:
intersight:
organizations:
- name: MyOrganization
policies:
boot_order:
- name: pxe-then-local
boot_mode: Uefi
secure_boot: true
boot_devices:
- name: pxe-primary
device_type: pxe_boot
interface_name: eth0
interface_source: name
ip_type: IPv4
- name: local-disk
device_type: local_disk
slot: MSTOR-RAID
bootloader:
name: bootx64.efi
path: \EFI\BOOT\
tags:
- key: env
value: prod
Example-2: The example below demonstrates a SAN boot policy for stateless servers where the OS resides on a remote LUN.