You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-nexus/howto-bare-metal-best-practices.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.reviewer: bartpinto
12
12
13
13
# Best practices for Bare Metal Machine operations
14
14
15
-
This article provides best practices for BareMetal Machine (BMM) lifecycle management operations.
15
+
This article provides best practices for Bare Metal Machine (BMM) lifecycle management operations.
16
16
The aim is to highlight common pitfalls and essential prerequisites.
17
17
18
18
## Read important disclaimers
@@ -76,7 +76,7 @@ Validate that there are no running firmware upgrade jobs through the BMC before
76
76
Interrupting an ongoing firmware upgrade can leave the Bare Metal Machine in an inconsistent state.
77
77
78
78
- You can view in the iDRAC GUI the `jobqueue` or use `run-read-command``racadm jobqueque view` to determine if there are firmware upgrade jobs running.
79
-
- For more information about the `run-read-command` feature, see [BareMetal Run-Read Execution](./howto-baremetal-run-read.md).
79
+
- For more information about the `run-read-command` feature, see [Bare Metal Run-Read Execution](./howto-baremetal-run-read.md).
80
80
81
81
```azurecli
82
82
az networkcloud baremetalmachine run-read-command \
0 commit comments