You must create a firmware media object for each type of firmware update. For example, if you are updating firmware for both BIOS and diagnostics, create two different media objects.
Observe the following:
- Bare Metal Orchestrator validates the firmware version against the version available in the sever for some firmware category. If the version provided in the firmware media is the same as that of the server, Bare Metal Orchestrator skips the firmware installation for the specific firmware. This optimization saves time, and thus allows quick onboarding of a server. The supported firmware category types are: BIOS, BMC, Network, CPLD, Chipset, Diagnostics, OSDriverPack, EnterpriseSolutions, FiberChannel, Memory, Power, SASDrive, SASNonRaid, SASRaid, SecureSystemManagement, SerialATA, SolidStateStorage, SystemManagement, DeviceFirmware, IdentityModule, and Other.Note: The Category field is mandatory for the creation of a firmware media object. A firmware media object cannot be created with a custom category type.
-
Update the
category
and theversion
correctly in the firmware media file, and the version must match with the actual version of firmware. For example, if executable file "BIOS_499DG_WN64_1.0.2.EXE" is used, then the version is 1.0.2. If executable file "iDRAC-with-Lifecycle-Controller_Firmware_WGTYV_WN64_5.00.20.10_A00.EXE" is used, then the version is 5.00.20.10. - If the same firmware version and category type is already present in the iDRAC, the firmware update will not be applied.
To create a firmware media object: