PDF(8.5 KB) View with Adobe Reader on a variety of devices
ePub(77.5 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(72.7 KB) View on Kindle device or Kindle app on multiple devices
Updated:July 30, 2019
Document ID:214692
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes a configuration example in order to restore Unified Extensible Firmware Interface (UEFI) boot table after Unified Computing System (UCS) motherboard replacement or BIOS upgrade that lead to an operating system boot failure.
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
UCS BIOS
UCS Boot Configuration
UEFI
Components Used
The information in this document is based on these software and hardware versions:
Cisco Integrated Management Controller (CIMC) 4.x
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Background Information
Motherboard was replaced or BIOS was upgraded and so the Operating System (OS) failed to boot possibly and displays an error message if previous boot mode, legacy or UEFI boot was changed after replacement or bios upgrade.
Message displayed might be "UEFI Interactive Shell v2.0 ... Error. No mapping found".
Problem
After UCS motherboard replacement or BIOS update, OS fails to boot.
The reason for the failure to boot the previously installed OS is due to the replacement motherboard can have different UEFI Boot Mode set than motherboard that was replaced, or BIOS upgrade caused this setting to revert or change to default.
Solution
Ensure that the boot mode matches settings that existed previous to motherboard replacement or BIOS upgrade.
For CIMC 4.x:
Step 1. Connect to CIMC ip through broswer.
Step 2. Select Menu button that is three horizontal lines.
Step 3. Select Compute.
Step 4. Select Configure Boot Order.
Step 5. Select UEFI or Legacy from the drop down menu Configured Boot Mode in order to match the previous setting.
Step 6. Select Save Changes.
Step 7. Reboot the server to have your configuration boot mode settings to take place.
Feedback