Skip to content

Commit 999c654

Browse files
committed
Update troubleshoot-reboot-reimage-replace.md
1 parent 41b3ec6 commit 999c654

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/operator-nexus/troubleshoot-reboot-reimage-replace.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ author: eak13
99
ms.author: ekarandjeff
1010
---
1111

12-
# Troubleshoot Azure Operator Nexus server problems
12+
# Troubleshoot Azure Operator Nexus Bare Metal Machine server problems
1313

14-
This article describes how to troubleshoot server problems by using restart, reimage, and replace actions on Azure Operator Nexus bare metal machines (BMMs). You might need to take these actions on your server for maintenance reasons, which causes a brief disruption to specific BMMs.
14+
This article describes how to troubleshoot server problems by using restart, reimage, and replace actions on Azure Operator Nexus bare metal machines (BMMs). You might need to take these actions on your server for maintenance reasons, which may cause a brief disruption to specific BMMs.
1515

1616
The time required to complete each of these actions is similar. Restarting is the fastest, whereas replacing takes slightly longer. All three actions are simple and efficient methods for troubleshooting.
1717

@@ -56,7 +56,7 @@ It's recommended to start with the least invasive solution (restart) and escalat
5656

5757
## Troubleshoot with a restart action
5858

59-
Restarting a BMM is a process of restarting the server through a simple API call. This action can be useful for troubleshooting problems when tenant virtual machines on the host aren't responsive or are otherwise stuck.
59+
Restarting a BMM is a process of restarting the server through a simple API call. This action can be useful for troubleshooting problems when Tenant Virtual Machines on the host aren't responsive or are otherwise stuck.
6060

6161
The restart typically is the starting point for mitigating a problem.
6262

@@ -174,7 +174,7 @@ az networkcloud baremetalmachine uncordon \
174174

175175
Servers contain many physical components that can fail over time. It is important to understand which physical repairs require BMM replacement and when BMM replacement is recommended.
176176

177-
A hardware validation process is invoked to ensure the integrity of the physical host in advance of deploying the OS image. Like the reimage action, the tenant data isn't modified during replacement.
177+
A hardware validation process is invoked to ensure the integrity of the physical host in advance of deploying the OS image. Like the reimage action, the Tenant data isn't modified during replacement.
178178

179179
> [!IMPORTANT]
180180
> Starting with the 2024-07-01 GA API version, the RAID controller is reset during BMM replace, wiping all data from the server's virtual disks. Baseboard Management Controller (BMC) virtual disk alerts triggered during BMM replace can be ignored unless there are additional physical disk and/or RAID controllers alerts.

0 commit comments

Comments
 (0)