Skip to content

Boot Order Policy

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.

Location in Intersight GUI: Policies » Boot Order

Diagram

policies (compute.intersight.organizations)

Section titled “policies (compute.intersight.organizations)”
NameTypeConstraintMandatoryDefault Value
boot_orderList[boot_order]No

boot_order (compute.intersight.organizations.policies)

Section titled “boot_order (compute.intersight.organizations.policies)”
NameTypeConstraintMandatoryDefault Value
nameStringRegex: ^[a-zA-Z0-9_.:-]{1,64}$Yes
descriptionStringNo
managedBooleantrue, falseNotrue
tagsList[tags]No
boot_modeChoiceUefi, LegacyNoUefi
secure_bootBooleantrue, falseNotrue
boot_devicesList[boot_devices]No

tags (compute.intersight.organizations.policies.boot_order)

Section titled “tags (compute.intersight.organizations.policies.boot_order)”
NameTypeConstraintMandatoryDefault Value
keyStringYes
valueStringYes

boot_devices (compute.intersight.organizations.policies.boot_order)

Section titled “boot_devices (compute.intersight.organizations.policies.boot_order)”
NameTypeConstraintMandatoryDefault Value
nameStringRegex: ^[a-zA-Z0-9_-]{1,30}$Yes
device_typeChoiceflex_mmc, http_boot, iscsi_boot, local_cdd, local_disk, nvme, pch_storage, pxe_boot, san_boot, sd_card, uefi_shell, usb, virtual_mediaYes
enabledBooleantrue, falseNotrue
slotStringNo
lunIntegermin: 0, max: 255No
subtypeChoiceNone, flex-util, flex-flash, SDCARD, cimc-mapped-dvd, cimc-mapped-hdd, kvm-mapped-dvd, kvm-mapped-hdd, kvm-mapped-fdd, usb-cd, usb-fdd, usb-hdd, flexmmc-mapped-dvd, flexmmc-mapped-hddNo
interface_nameStringNo
interface_sourceChoicename, mac, portNo
ip_typeChoiceNone, IPv4, IPv6No
ip_config_typeChoiceDHCP, StaticNo
mac_addressStringNo
portIntegermin: -1, max: 255No
protocolChoiceHTTP, HTTPSNo
target_wwpnStringNo
uriStringNo
ipv4_configClass[ipv4_config]No
ipv6_configClass[ipv6_config]No
bootloaderClass[bootloader]No

ipv4_config (compute.intersight.organizations.policies.boot_order.boot_devices)

Section titled “ipv4_config (compute.intersight.organizations.policies.boot_order.boot_devices)”
NameTypeConstraintMandatoryDefault Value
ipIPYes
network_maskStringYes
gateway_ipIPYes
dns_ipIPNo

ipv6_config (compute.intersight.organizations.policies.boot_order.boot_devices)

Section titled “ipv6_config (compute.intersight.organizations.policies.boot_order.boot_devices)”
NameTypeConstraintMandatoryDefault Value
ipIPYes
prefix_lengthIntegermin: 1, max: 128Yes
gateway_ipIPYes
dns_ipIPNo

bootloader (compute.intersight.organizations.policies.boot_order.boot_devices)

Section titled “bootloader (compute.intersight.organizations.policies.boot_order.boot_devices)”
NameTypeConstraintMandatoryDefault Value
nameStringYes
pathStringYes
descriptionStringNo

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.

compute:
intersight:
organizations:
- name: MyOrganization
policies:
boot_order:
- name: san-boot
boot_mode: Uefi
boot_devices:
- name: san-primary
device_type: san_boot
interface_name: vhba0
lun: 0
target_wwpn: "20:00:00:25:b5:00:00:01"
bootloader:
name: bootx64.efi
path: \EFI\BOOT\