@@ -71,31 +71,35 @@ The restart typically is the starting point for mitigating a problem.
71
71
> The restart operation is the fastest recovery method but may not resolve issues related to OS corruption or hardware failures.
72
72
73
73
** The following Azure CLI command will ` power-off ` the specified bareMetalMachineName:**
74
- ```
74
+
75
+ ``` azurecli
75
76
az networkcloud baremetalmachine power-off \
76
77
--name <bareMetalMachineName> \
77
78
--resource-group "<resourceGroup>" \
78
79
--subscription <subscriptionID>
79
80
```
80
81
81
82
** The following Azure CLI command will ` start ` the specified bareMetalMachineName:**
82
- ```
83
+
84
+ ``` azurecli
83
85
az networkcloud baremetalmachine start \
84
86
--name <bareMetalMachineName> \
85
87
--resource-group "<resourceGroup>" \
86
88
--subscription <subscriptionID>
87
89
```
88
90
89
91
** The following Azure CLI command will ` restart ` the specified bareMetalMachineName:**
90
- ```
92
+
93
+ ``` azurecli
91
94
az networkcloud baremetalmachine restart \
92
95
--name <bareMetalMachineName> \
93
96
--resource-group "<resourceGroup>" \
94
97
--subscription <subscriptionID>
95
98
```
96
99
97
100
** To verify the BMM status after restart:**
98
- ```
101
+
102
+ ``` azurecli
99
103
az networkcloud baremetalmachine show \
100
104
--name <bareMetalMachineName> \
101
105
--resource-group "<resourceGroup>" \
@@ -125,6 +129,7 @@ A reimage action is the best practice for lowest operational risk to ensure the
125
129
** To identify if any workloads are currently running on a BMM, run the following command:**
126
130
127
131
** For Virtual Machines:**
132
+
128
133
``` azurecli
129
134
az networkcloud baremetalmachine show -n <nodeName> \
130
135
--resource-group <resourceGroup> \
@@ -138,7 +143,8 @@ kubectl get nodes <resourceName> -ojson |jq '.metadata.labels."topology.kubernet
138
143
```
139
144
140
145
** The following Azure CLI command will ` cordon ` the specified bareMetalMachineName.**
141
- ```
146
+
147
+ ``` azurecli
142
148
az networkcloud baremetalmachine cordon \
143
149
--evacuate "True" \
144
150
--name <bareMetalMachineName> \
@@ -147,15 +153,17 @@ az networkcloud baremetalmachine cordon \
147
153
```
148
154
149
155
** The following Azure CLI command will ` reimage ` the specified bareMetalMachineName.**
150
- ```
156
+
157
+ ``` azurecli
151
158
az networkcloud baremetalmachine reimage \
152
159
--name <bareMetalMachineName> \
153
160
--resource-group "<resourceGroup>" \
154
161
--subscription <subscriptionID>
155
162
```
156
163
157
164
** The following Azure CLI command will ` uncordon ` the specified bareMetalMachineName.**
158
- ```
165
+
166
+ ``` azurecli
159
167
az networkcloud baremetalmachine uncordon \
160
168
--name <bareMetalMachineName> \
161
169
--resource-group "<resourceGroup>" \
@@ -180,7 +188,8 @@ A hardware validation process is invoked to ensure the integrity of the physical
180
188
5 . ** Verify status** - Check that the BMM is properly functioning
181
189
182
190
** The following Azure CLI command will ` cordon ` the specified bareMetalMachineName.**
183
- ```
191
+
192
+ ``` azurecli
184
193
az networkcloud baremetalmachine cordon \
185
194
--evacuate "True" \
186
195
--name <bareMetalMachineName> \
@@ -213,7 +222,8 @@ When you're performing the following physical repairs, a replace action ***is re
213
222
After physical repairs are completed, perform a replace action.
214
223
215
224
** The following Azure CLI command will ` replace ` the specified bareMetalMachineName.**
216
- ```
225
+
226
+ ``` azurecli
217
227
az networkcloud baremetalmachine replace \
218
228
--name <bareMetalMachineName> \
219
229
--resource-group "<resourceGroup>" \
@@ -226,7 +236,8 @@ az networkcloud baremetalmachine replace \
226
236
```
227
237
228
238
** The following Azure CLI command will uncordon the specified bareMetalMachineName.**
229
- ```
239
+
240
+ ``` azurecli
230
241
az networkcloud baremetalmachine uncordon \
231
242
--name <bareMetalMachineName> \
232
243
--resource-group "<resourceGroup>" \
0 commit comments