Skip to content

Update firmware guidelines for deployment #4054

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sirajyasin wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update firmware guidelines for deployment #4054

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9c28576
Update firmware guidelines for deployment
sirajyasin Dec 17, 2025
77c1a4b
grammar fix
v-dirichards Dec 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions operator-nexus/howto-platform-prerequisites.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -682,6 +682,11 @@ An example design of three on-premises instances from the same NFC/CM pair, usin
As a best practice, the following BIOS and firmware versions need to be installed on the servers prior to deployment, based on the selected runtime version and BOM.
For reference, version N is the latest available runtime version. N-1 and N-2 are the previous supported runtime versions.

>[!NOTE]
> iDRAC versions earlier than 7.20.30.50 had known limitations with firmware downgrade support. As a result, if a target system was running newer firmware on any component (BIOS, PERC, Broadcom, Mellanox, CPLD), iDRAC would not flag the mismatch and would skip the downgrade. This behavior was corrected starting with iDRAC 7.20.30.50.
>
> Although the newer iDRAC versions make a best-effort attempt to align component firmware with the catalog for the given runtime, certain downgrade scenarios may trigger attribute rollbacks that can lead to BIOS corruption, as documented by Dell. For this reason, the recommended practice is to ensure that all component firmware versions are equal to or lower than the versions listed for the corresponding runtime release.

#### Nexus Cluster runtime version N

##### BOM 1.7.3
Expand Down