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/troubleshoot-reboot-reimage-replace.md
+32-32Lines changed: 32 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,25 +56,25 @@ The restart typically is the starting point for mitigating a problem.
56
56
***The following Azure CLI command will `power-off` the specified bareMetalMachineName.***
57
57
```
58
58
az networkcloud baremetalmachine power-off \
59
-
--name "bareMetalMachineName" \
60
-
--resource-group "cluster_MRG" \
61
-
--subscription "subscription_ID"
59
+
--name <bareMetalMachineName> \
60
+
--resource-group <CLUSTER_MRG> \
61
+
--subscription <SUBSCRIPTION_ID>
62
62
```
63
63
64
64
***The following Azure CLI command will `start` the specified bareMetalMachineName.***
65
65
```
66
66
az networkcloud baremetalmachine start \
67
-
--name "bareMetalMachineName" \
68
-
--resource-group "cluster_MRG" \
69
-
--subscription "subscription_ID"
67
+
--name <bareMetalMachineName> \
68
+
--resource-group <CLUSTER_MRG> \
69
+
--subscription <SUBSCRIPTION_ID>
70
70
```
71
71
72
72
***The following Azure CLI command will `restart` the specified bareMetalMachineName.***
73
73
```
74
74
az networkcloud baremetalmachine restart \
75
-
--name "bareMetalMachineName" \
76
-
--resource-group "cluster_MRG" \
77
-
--subscription "subscription_ID"
75
+
--name <bareMetalMachineName> \
76
+
--resource-group <CLUSTER_MRG> \
77
+
--subscription <SUBSCRIPTION_ID>
78
78
```
79
79
80
80
@@ -93,25 +93,25 @@ As a best practice, make sure the BMM's workloads are drained using the cordon c
93
93
```
94
94
az networkcloud baremetalmachine cordon \
95
95
--evacuate "True" \
96
-
--name "bareMetalMachineName" \
97
-
--resource-group "cluster_MRG" \
98
-
--subscription "subscription_ID"
96
+
--name <bareMetalMachineName> \
97
+
--resource-group <CLUSTER_MRG> \
98
+
--subscription <SUBSCRIPTION_ID>
99
99
```
100
100
101
101
***The following Azure CLI command will `reimage` the specified bareMetalMachineName.***
102
102
```
103
103
az networkcloud baremetalmachine reimage \
104
-
–-name "bareMetalMachineName" \
105
-
--resource-group "cluster_MRG" \
106
-
--subscription "subscription_ID"
104
+
–-name <bareMetalMachineName> \
105
+
--resource-group <CLUSTER_MRG> \
106
+
--subscription <SUBSCRIPTION_ID>
107
107
```
108
108
109
109
***The following Azure CLI command will `uncordon` the specified bareMetalMachineName.***
110
110
```
111
111
az networkcloud baremetalmachine uncordon \
112
-
--name "bareMetalMachineName" \
113
-
--resource-group "cluster_MRG" \
114
-
--subscription "subscription_ID"
112
+
--name <bareMetalMachineName> \
113
+
--resource-group <CLUSTER_MRG> \
114
+
--subscription <SUBSCRIPTION_ID>
115
115
```
116
116
117
117
## Troubleshoot with a replace action
@@ -129,9 +129,9 @@ As a best practice, first issue a `cordon` command to remove the bare metal mach
129
129
```
130
130
az networkcloud baremetalmachine cordon \
131
131
--evacuate "True" \
132
-
--name "bareMetalMachineName" \
133
-
--resource-group "cluster_MRG" \
134
-
--subscription "subscription_ID"
132
+
--name <bareMetalMachineName> \
133
+
--resource-group <CLUSTER_MRG> \
134
+
--subscription <SUBSCRIPTION_ID>
135
135
```
136
136
137
137
When you're performing a physical hot swappable power supply repair, a replace action is not required because the BMM host will continue to function normally after the repair.
@@ -159,22 +159,22 @@ After physical repairs are completed, perform a replace action.
159
159
***The following Azure CLI command will `replace` the specified bareMetalMachineName.***
0 commit comments