Skip to content

Commit f07c76a

Browse files
committed
Update troubleshoot-reboot-reimage-replace.md
1 parent 999c654 commit f07c76a

File tree

1 file changed

+17
-17
lines changed

1 file changed

+17
-17
lines changed

articles/operator-nexus/troubleshoot-reboot-reimage-replace.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -62,10 +62,10 @@ The restart typically is the starting point for mitigating a problem.
6262

6363
### Restart workflow
6464

65-
1. **Assess impact** - Determine if restarting the BMM will impact critical workloads
66-
2. **Power off** - If needed, power off the BMM (optional)
67-
3. **Start or restart** - Either start a powered-off BMM or restart a running BMM
68-
4. **Verify status** - Check if the BMM is back online and functioning properly
65+
1. **Assess impact** - Determine if restarting the BMM will impact critical workloads.
66+
1. **Power off** - If needed, power off the BMM (optional).
67+
1. **Start or restart** - Either start a powered-off BMM or restart a running BMM.
68+
1. **Verify status** - Check if the BMM is back online and functioning properly.
6969

7070
> [!NOTE]
7171
> The restart operation is the fastest recovery method but may not resolve issues related to OS corruption or hardware failures.
@@ -117,10 +117,10 @@ A reimage action is the best practice for lowest operational risk to ensure the
117117

118118
### Reimage workflow
119119

120-
1. **Verify running workloads** - Before reimaging, check what workloads are running on the BMM
121-
2. **Cordon and evacuate workloads** - Drain the BMM of workloads
122-
3. **Perform reimage** - Execute the reimage operation
123-
4. **Uncordon** - Make the BMM schedulable again after reimage completes
120+
1. **Verify running workloads** - Before reimaging, check what workloads are running on the BMM.
121+
1. **Cordon and evacuate workloads** - Drain the BMM of workloads.
122+
1. **Perform reimage** - Execute the reimage operation.
123+
1. **Uncordon** - Make the BMM schedulable again after reimage completes.
124124

125125
> [!WARNING]
126126
> Running more than one `baremetalmachine replace` or `reimage` command at the same time, or running a `replace`
@@ -181,11 +181,11 @@ A hardware validation process is invoked to ensure the integrity of the physical
181181
182182
### Replace workflow
183183

184-
1. **Cordon and evacuate** - Remove workloads from the BMM before physical repair
185-
2. **Perform physical repairs** - Replace hardware components as needed
186-
3. **Execute replace command** - Run the replace command with required parameters
187-
4. **Uncordon** - Make the BMM schedulable again after replacement completes
188-
5. **Verify status** - Check that the BMM is properly functioning
184+
1. **Cordon and evacuate** - Remove workloads from the BMM before physical repair.
185+
1. **Perform physical repairs** - Replace hardware components as needed.
186+
1. **Execute replace command** - Run the replace command with required parameters.
187+
1. **Uncordon** - Make the BMM schedulable again after replacement completes.
188+
1. **Verify status** - Check that the BMM is properly functioning.
189189

190190
**The following Azure CLI command will `cordon` the specified bareMetalMachineName.**
191191

@@ -257,10 +257,10 @@ Restarting, reimaging, and replacing are effective troubleshooting methods for a
257257
### Best practices
258258

259259
1. **Always follow the escalation path**: Start with restart, then reimage, then replace unless the issue clearly indicates otherwise.
260-
2. **Verify workloads before action**: Use the provided commands to identify running workloads before any disruptive action.
261-
3. **Cordon with evacuation**: When performing reimage or replace actions, always use `cordon` with `evacuate="True"` to safely move workloads.
262-
4. **Never run multiple operations simultaneously**: Ensure one operation completes before starting another to prevent server issues.
263-
5. **Verify resolution**: After performing any action, verify the BMM status and that the original issue is resolved.
260+
1. **Verify workloads before action**: Use the provided commands to identify running workloads before any disruptive action.
261+
1. **Cordon with evacuation**: When performing reimage or replace actions, always use `cordon` with `evacuate="True"` to safely move workloads.
262+
1. **Never run multiple operations simultaneously**: Ensure one operation completes before starting another to prevent server issues.
263+
1. **Verify resolution**: After performing any action, verify the BMM status and that the original issue is resolved.
264264

265265
More details about the BMM actions can be found in the [BMM actions](howto-baremetal-functions.md) article.
266266

0 commit comments

Comments
 (0)