Skip to content

Commit 3b3b940

Browse files
Merge pull request #239421 from JAC0BSMITH/jac0bsmithNexusDocs
Refinement to BMM actions
2 parents 4dd9a70 + 7f99004 commit 3b3b940

File tree

1 file changed

+39
-20
lines changed

1 file changed

+39
-20
lines changed

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

Lines changed: 39 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: harish6724
55
ms.author: harishrao
66
ms.service: azure-operator-nexus
77
ms.topic: how-to
8-
ms.date: 03/06/2023
8+
ms.date: 05/26/2023
99
ms.custom: template-how-to
1010
---
1111

@@ -15,40 +15,56 @@ This article describes how to perform lifecycle management operations on Bare Me
1515

1616
- Power off the BMM
1717
- Start the BMM
18+
- Restart the BMM
1819
- Make the BMM unschedulable or schedulable
19-
- Reinstall the BMM image
20-
- Replace BMM
20+
- Reimage the BMM
21+
- Replace the BMM
2122

2223
## Prerequisites
2324

2425
1. Install the latest version of the
2526
[appropriate CLI extensions](./howto-install-cli-extensions.md)
26-
1. Ensure that the target bare metal machine (server) must have its `poweredState` set to `On` and have its `readyState` set to `True`
27-
1. Get the Resource group name that you created for `Cluster` resource
27+
1. Get the name of the resource group for the BMM
28+
1. Get the name of the bare metal machine that requires a lifecycle management operation
29+
1. Ensure that the target bare metal machine `poweredState` set to `On` and `readyState` set to `True`
30+
1. This prerequisite is not applicable for the `start` command
31+
2832

2933
## Power off the BMM
3034

3135
This command will `power-off` the specified `bareMetalMachineName`.
3236

3337
```azurecli
34-
az networkcloud baremetalmachine power-off --name "bareMetalMachineName" \
35-
--resource-group "resourceGroupName"
38+
az networkcloud baremetalmachine power-off \
39+
--name "bareMetalMachineName" \
40+
--resource-group "resourceGroupName"
3641
```
3742

3843
## Start the BMM
3944

4045
This command will `start` the specified `bareMetalMachineName`.
4146

4247
```azurecli
43-
az networkcloud baremetalmachine start --name "bareMetalMachineName" \
48+
az networkcloud baremetalmachine start \
49+
--name "bareMetalMachineName" \
50+
--resource-group "resourceGroupName"
51+
```
52+
53+
## Restart the BMM
54+
55+
This command will `restart` the specified `bareMetalMachineName`.
56+
57+
```azurecli
58+
az networkcloud baremetalmachine restart \
59+
--name "bareMetalMachineName" \
4460
--resource-group "resourceGroupName"
4561
```
4662

4763
## Make a BMM unschedulable (cordon)
4864

4965
You can make a BMM unschedulable by executing the [`cordon`](#make-a-bmm-unschedulable-cordon) command.
5066
On the execution of the `cordon` command,
51-
Operator Nexus workloads are not scheduled on the BMM when cordon is set; any attempt to create a workload on a `cordoned`
67+
Operator Nexus workloads aren't scheduled on the BMM when cordon is set; any attempt to create a workload on a `cordoned`
5268
BMM results in the workload being set to `pending` state. Existing workloads continue to run.
5369
The cordon command supports an `evacuate` parameter with the default `False` value.
5470
On executing the `cordon` command, with the value `True` for the `evacuate`
@@ -74,26 +90,29 @@ state on the BMM are `restarted` when the BMM is `uncordoned`.
7490
--resource-group "resourceGroupName"
7591
```
7692

77-
## Reimage a BMM (reinstall a BMM image)
93+
## Reimage a BMM
7894

79-
An existing BMM image is **reinstalled** using the `reimage` command. This command doesn't install a new image.
80-
Make sure the BMM's workloads are drained using the [`cordon`](#make-a-bmm-unschedulable-cordon)
95+
You can restore the runtime version on a BMM by executing `reimage` command. This process **redeploys** the runtime image on the target BMM and executes the steps to rejoin the cluster with the same identifiers. This action doesn't impact the tenant workload files on this BMM.
96+
As a best practice, make sure the BMM's workloads are drained using the [`cordon`](#make-a-bmm-unschedulable-cordon)
8197
command, with `evacuate "True"`, prior to executing the `reimage` command.
8298

8399
```azurecli
84-
az networkcloud baremetalmachine reimage –-name "bareMetalMachineName" \
100+
az networkcloud baremetalmachine reimage \
101+
–-name "bareMetalMachineName" \
85102
--resource-group "resourceGroupName"
86103
```
87104

88-
The reimage command restarts the BMM and uncordons it. The re-imaged BMM will have an IP address.You can start deploying workloads on the reimaged BMM.
89-
90105
## Replace BMM
91106

92-
Use `Replace BMM` command whenever a BareMetal machine has encountered hardware issues requiring a complete or partial hardware replacement. After replace the MAC address of Baremetal Host will change, however the IDrac IP address and hostname will remain the same.
107+
Use `Replace BMM` command when a server has encountered hardware issues requiring a complete or partial hardware replacement. After replacement of components such as motherboard or NIC replacement, the MAC address of BMM will change, however the IDrac IP address and hostname will remain the same.
93108

94109
```azurecli
95-
az networkcloud baremetalmachine replace --name "bareMetalMachineName" \
96-
--bmc-credentials password="{password}" username="bmcuser" --bmc-mac-address "00:00:4f:00:57:ad" \
97-
--boot-mac-address "00:00:4e:00:58:af" --machine-name "name" --serial-number "BM1219XXX" \
98-
--resource-group "resourceGroupName"
110+
az networkcloud baremetalmachine replace \
111+
--name "bareMetalMachineName" \
112+
--resource-group "resourceGroupName" \
113+
--bmc-credentials password="{password}" username="{user}" \
114+
--bmc-mac-address "00:00:4f:00:57:ad" \
115+
--boot-mac-address "00:00:4e:00:58:af" \
116+
--machine-name "name" \
117+
--serial-number "BM1219XXX"
99118
```

0 commit comments

Comments
 (0)