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-baremetal-functions.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,14 +16,14 @@ This article describes how to perform lifecycle management operations on bare me
16
16
> [!CAUTION]
17
17
> Do not perform any action against management servers without first consulting with Microsoft support personnel. Doing so could affect the integrity of the Operator Nexus Cluster.
18
18
19
-
-**Power off the BMM**
20
-
- Start the BMM
21
-
-**Restart the BMM**
22
-
- Make the BMM unschedulable (cordon without evacuate)
23
-
-**Make the BMM unschedulable (cordon with evacuate)**
24
-
- Make the BMM schedulable (uncordon)
25
-
-**Reimage the BMM**
26
-
-**Replace the BMM**
19
+
-**Power off a BMM**
20
+
- Start a BMM
21
+
-**Restart a BMM**
22
+
- Make a BMM unschedulable (cordon without evacuate)
23
+
-**Make a BMM unschedulable (cordon with evacuate)**
24
+
- Make a BMM schedulable (uncordon)
25
+
-**Reimage a BMM**
26
+
-**Replace a BMM**
27
27
28
28
> [!IMPORTANT]
29
29
> Disruptive command requests against a Kubernetes Control Plane (KCP) node are rejected if there is another disruptive action command already running against another KCP node or if the full KCP is not available. This check is done to maintain the integrity of the Nexus instance and ensure multiple KCP nodes don't become non-operational at once due to simultaneous disruptive actions. If multiple nodes become non-operational, it will break the healthy quorum threshold of the Kubernetes Control Plane.
@@ -41,7 +41,7 @@ This article describes how to perform lifecycle management operations on bare me
41
41
1. Ensure that the target bare metal machine `poweredState` set to `On` and `readyState` set to `True`.
42
42
1. This prerequisite isn't applicable for the `start` command.
43
43
44
-
## Power off the BMM
44
+
## Power off a BMM
45
45
46
46
This command will `power-off` the specified `bareMetalMachineName`.
47
47
@@ -52,7 +52,7 @@ az networkcloud baremetalmachine power-off \
52
52
--subscription <SUBSCRIPTION_ID>
53
53
```
54
54
55
-
## Start the BMM
55
+
## Start a BMM
56
56
57
57
This command will `start` the specified `bareMetalMachineName`.
58
58
@@ -63,7 +63,7 @@ az networkcloud baremetalmachine start \
63
63
--subscription <SUBSCRIPTION_ID>
64
64
```
65
65
66
-
## Restart the BMM
66
+
## Restart a BMM
67
67
68
68
This command will `restart` the specified `bareMetalMachineName`.
69
69
@@ -125,7 +125,7 @@ az networkcloud baremetalmachine reimage \
125
125
--subscription <SUBSCRIPTION_ID>
126
126
```
127
127
128
-
## Replace BMM
128
+
## Replace a BMM
129
129
130
130
Use the `replace` command when a server encounters hardware issues requiring a complete or partial hardware replacement. After replacement of components such as motherboard or Network Interface Card (NIC) replacement, the MAC address of BMM will change, however the iDRAC IP address and hostname will remain the same.
0 commit comments