From ff67a4d3d8d5e1f86dddf50266464e32dfd91fe3 Mon Sep 17 00:00:00 2001
From: sirajyasin <38433478+sirajyasin@users.noreply.github.com>
Date: Wed, 17 Dec 2025 14:25:59 -0600
Subject: [PATCH] Update troubleshooting steps for hardware replacement

Added firmware verification steps before replacement action.
---
 operator-nexus/troubleshoot-reboot-reimage-replace.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/operator-nexus/troubleshoot-reboot-reimage-replace.md b/operator-nexus/troubleshoot-reboot-reimage-replace.md
index 24d69333b6..d8bab1e07d 100644
--- a/operator-nexus/troubleshoot-reboot-reimage-replace.md
+++ b/operator-nexus/troubleshoot-reboot-reimage-replace.md
@@ -242,7 +242,9 @@ When you're performing the following physical repairs, a replace action **_is re
 - Mellanox Network Interface Card (NIC)
 - Broadcom embedded NIC
 
-After physical repairs are completed, perform a replace action.
+After physical repairs are completed, verify that all firmware versions align with the versions supported for the corresponding runtime. Apply the same best‑practice checks used during deployment to ensure the components meet the [minimum firmware requirements](/operator-nexus/howto-platform-prerequisites.md#minimum-recommended-bios-and-firmware-versions-for-nexus-cluster-runtime).
+
+Once the firmware checks are complete, proceed with the replace action.
 
 **The following Azure CLI command will `replace` the specified bareMetalMachineName.**