Skip to content

Commit f1f0898

Browse files
authored
Standardize BMM terminology in documentation
1 parent 93f7cf4 commit f1f0898

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/operator-nexus/howto-baremetal-functions.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -16,14 +16,14 @@ This article describes how to perform lifecycle management operations on bare me
1616
> [!CAUTION]
1717
> 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.
1818
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**
2727

2828
> [!IMPORTANT]
2929
> 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
4141
1. Ensure that the target bare metal machine `poweredState` set to `On` and `readyState` set to `True`.
4242
1. This prerequisite isn't applicable for the `start` command.
4343

44-
## Power off the BMM
44+
## Power off a BMM
4545

4646
This command will `power-off` the specified `bareMetalMachineName`.
4747

@@ -52,7 +52,7 @@ az networkcloud baremetalmachine power-off \
5252
--subscription <SUBSCRIPTION_ID>
5353
```
5454

55-
## Start the BMM
55+
## Start a BMM
5656

5757
This command will `start` the specified `bareMetalMachineName`.
5858

@@ -63,7 +63,7 @@ az networkcloud baremetalmachine start \
6363
--subscription <SUBSCRIPTION_ID>
6464
```
6565

66-
## Restart the BMM
66+
## Restart a BMM
6767

6868
This command will `restart` the specified `bareMetalMachineName`.
6969

@@ -125,7 +125,7 @@ az networkcloud baremetalmachine reimage \
125125
--subscription <SUBSCRIPTION_ID>
126126
```
127127

128-
## Replace BMM
128+
## Replace a BMM
129129

130130
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.
131131

0 commit comments

Comments
 (0)