Server Boot Order
Using Cisco IMC, you can configure the order in which the server attempts to boot from available boot device types. In the legacy boot order configuration, Cisco IMC allows you to reorder the device types but not the devices within the device types. With the precision boot order configuration, you can have a linear ordering of the devices. In the web UI or CLI you can change the boot order and boot mode, add multiple devices under each device types, rearrange the boot order, set parameters for each device type.
When you change the boot order configuration, Cisco IMC sends the configured boot order to BIOS the next time that server is rebooted. To implement the new boot order, reboot the server after you make the configuration change. The new boot order takes effect on any subsequent reboot. The configured boot order remains until the configuration is changed again in Cisco IMC or in the BIOS setup.
Note |
The actual boot order differs from the configured boot order if either of the following conditions occur:
|
Note |
When you create a new policy using the configure boot order feature, BIOS tries to map this new policy to the devices in the system. It displays the actual device name and the policy name to which it is mapped in the Actual Boot Order area. If BIOS cannot map any device to a particular policy in Cisco IMC, the actual device name is stated as NonPolicyTarget in the Actual Boot Order area. |
Note |
When you upgrade Cisco IMC to the latest version 2.0(x) for the first time, the legacy boot order is migrated to the precision boot order. During this process, previous boot order configuration is erased and all device types configured before updating to 2.0 version are converted to corresponding precision boot device types and some dummy devices are created for the same device types. you can view these devices in the Configured Boot Order area in the web UI. To view these devices in the CLI, enter show boot-device command. During this the server's actual boot order is retained and it can be viewed under actual boot order option in web UI and CLI. |
When you downgrade Cisco IMC prior to 2.0(x) verison the server's last legacy boot order is retained, and the same can be viewed under Actual Boot Order area. For example:
-
If you configured the server in a legacy boot order in 2.0(x) version, upon downgrade a legacy boot order configuration is retained.
-
If you configured the server in a precision boot order in 2.0(x), upon downgrade the last configured legacy boot order is retained.
Important |
|
Configuring the Precision Boot Order
Before you begin
You must log in as a user with admin privileges to configure server the boot order.
Procedure
Step 1 |
In the Navigation pane, click the Compute menu. |
||||||||||||||||||||||||||||||
Step 2 |
In the BIOS tab, click the Configure Boot Order tab. |
||||||||||||||||||||||||||||||
Step 3 |
In the BIOS Properties area, click Configure Boot Order. A dialog box with boot order instructions appears. |
||||||||||||||||||||||||||||||
Step 4 |
In the Configure Boot Order dialog box, update the following properties:
|
||||||||||||||||||||||||||||||
Step 5 |
Click Save Changes. Additional device types might be appended to the actual boot order, depending on what devices you have connected to your server. |
What to do next
Reboot the server to boot with your new boot order.
Managing a Boot Device
Before you begin
You must log in as a user with admin privileges to add device type to the server boot order.
Procedure
Step 1 |
In the Navigation pane, click the Compute menu. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 2 |
In the BIOS tab, click the Configure Boot Order tab. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 3 |
In the BIOS Properties area, click Configure Boot Order. A dialog box with boot order instructions appears. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Step 4 |
In the Configure Boot Order dialog box, from the Add Boot Device table, choose the device that you want add to the boot order. To add the local HDD device, click Add Local HDD, and update the following parameters:
To add the PXE device, click Add PXE, and update the following parameters:
To add the SAN boot device, click Add SAN Boot, and update the following parameters:
To add the iSCSI boot device, click Add iSCSI Boot, and update the following parameters:
To add the SD card, click Add SD Card, and update the following parameters:
To add the USB device, click Add USB, and update the following parameters:
To add the virtual media, click Virtual Media, and update the following parameters:
To add the PCH storage device, click PCH Storage, and update the following parameters:
To add the UEFI shell device, click Add UEFI Shell, and update the following parameters:
|
Overview to UEFI Secure Boot
You can use Unified Extensible Firmware Interface (UEFI) secure boot to ensure that all the EFI drivers, EFI applications, option ROM or operating systems prior to loading and execution are signed and verified for authenticity and integrity, before you load and execute the operating system. You can enable this option using either web UI or CLI. When you enable UEFI secure boot mode, the boot mode is set to UEFI mode and you cannot modify the configured boot mode until the UEFI boot mode is disabled.
Note |
If you enable UEFI secure boot on a nonsupported OS, on the next reboot, you cannot boot from that particular OS. If you try to boot from the previous OS, an error is reported and recorded the under system software event in the web UI. You must disable the UEFI secure boot option using Cisco IMC to boot from your previous OS. |
Important |
Also, if you use an unsupported adapter, an error log event in Cisco IMC SEL is recorded. The error messages is displayed that says: System Software event: Post sensor, System Firmware error. EFI Load Image Security Violation. [0x5302] was asserted . |
Components | Types |
---|---|
Supported OS |
|
Broadcom PCI adapters |
|
Intel PCI adapters |
|
QLogic PCI adapters |
|
Fusion-io |
|
LSI |
|
Enabling UEFI Secure Boot
Procedure
Step 1 |
In the Navigation pane, click the Compute menu. |
||
Step 2 |
In the work pane, click the BIOS tab. |
||
Step 3 |
In the BIOS Properties area of the Configure Boot Order tab, check UEFI Secure Boot checkbox.
If you enable UEFI secure boot on a nonsupported OS, on the next reboot, you cannot boot from that particular OS. If you try to boot from the previous OS, an error is reported and recorded under the system software event in the web UI. You must disable the UEFI secure boot option by using Cisco IMC to boot from your previous OS. |
||
Step 4 |
Click Save Changes. |
What to do next
Reboot the server to have your configuration boot mode settings take place.
Disabling UEFI Secure Boot
Procedure
Step 1 |
In the Navigation pane, click the Compute menu. |
Step 2 |
In the work pane, click the BIOS tab. |
Step 3 |
In the BIOS Properties area, uncheck the UEFI Secure Boot check box. |
Step 4 |
Click Save Changes. |
What to do next
Reboot the server to have your configuration boot mode settings take place.
Viewing the Actual Server Boot Order
The actual server boot order is the boot order actually used by BIOS when the server last booted. The actual boot order can differ from the boot order configured in Cisco IMC.
Procedure
Step 1 |
In the Navigation pane, click the Compute menu. |
||||
Step 2 |
In the BIOS tab, click the Configure Boot Order tab. |
||||
Step 3 |
In the BIOS Properties area, click Configure Boot Order. This area displays the boot order devices configured through Cisco IMC as well as the actual boot order used by the server BIOS. The Configured Boot Devices section displays the boot order (Basic or Advanced) configured through Cisco IMC. If this configuration changes, Cisco IMC sends this boot order to BIOS the next time that server boots. The Basic configuration allows you to specify only the device type. The Advanced configuration allows you to configure the device with specific parameters such as slot, port and LUN. To change the configured boot order, or to restore the previously configured boot order, administrators can click the Configure Boot Order button. To have these changes take effect immediately, reboot the server. You can verify the new boot order by refreshing the BIOS tab.
The Actual Boot Devices section displays the boot order actually used by BIOS when the server last booted. The actual boot order will differ from the configured boot order if either of the following conditions occur:
|
Configuring a Server to Boot With a One-Time Boot Device
You can configure a server to boot from a particular device only for the next server boot, without disrupting the currently configured boot order. Once the server boots from the one time boot device, all its future reboots occur from the previously configured boot order.
Before you begin
You must log in as a user with admin privileges to configure server the boot order.
Procedure
Step 1 |
In the Navigation pane, click the Compute menu. |
||
Step 2 |
In the BIOS tab, click the Configure Boot Order tab. |
||
Step 3 |
In the BIOS Properties area, select an option from the Configured One Time Boot Device drop-down.
|
Creating a Server Asset Tag
Before you begin
You must log in with user or admin privileges to perform this task.
Procedure
Step 1 |
In the Navigation pane, click the Chassis menu. |
Step 2 |
In the Chassis menu, click Summary. |
Step 3 |
In the Server Properties area, update the Asset Tag field. |
Step 4 |
Click Save Changes. |