How do I record BIOS and management-controller firmware versions before an update?
Firmware updates must match the exact server or component model and its supported upgrade path. Inventory the current versions before reviewing release notes or advisories. The BIOS, BMC, storage controller, NIC and drive firmware are separate components and may have different dependencies and restart requirements.
Before you start
- Authorised inventory access; local IPMI support for the BMC command.
Instructions
1. Read BIOS information
Use a targeted DMI query. Firmware-reported data is useful for matching documentation, but verify the model and service identifier through the provider or manufacturer record.
sudo dmidecode --type biosRecord the version and release date. A newer date alone does not establish that a particular update is necessary or compatible.
2. Read the management-controller version
On a platform supporting local IPMI, query controller information without changing it.
sudo ipmitool -I open mc infoUse the returned product and firmware details to select the exact vendor documentation. Do not upload a firmware file selected only by a similar product name.
Check the result
- The change plan identifies each component, current and target versions, compatibility prerequisites, expected interruption and post-update checks.
Troubleshooting
- The OS tool cannot report the controller version
- Use the authenticated BMC or provider inventory interface; do not infer the version from the server’s OS release.
- An update requires intermediate versions
- Follow the supported sequence and recovery guidance instead of skipping steps for speed.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.