Update and rename troubleshoot-baremetalmachine-provisioning.md to troubleshoot-bmm-provisioning.md

Update document name, corrections from PR review and acrolinx corrections.

Author: bartpinto

articles/operator-nexus/troubleshoot-baremetalmachine-provisioning.md renamed to articles/operator-nexus/troubleshoot-bmm-provisioning.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Operator Nexus Troubleshooting BareMetal Machine Provisioning
-description: Troubleshoot BareMetal Machine Provisioning for Azure Operator Nexus.
+title: Azure Operator Nexus troubleshooting BMM provisioning
+description: Troubleshoot BMM provisioning for Azure Operator Nexus.
 ms.service: azure-operator-nexus
 ms.custom: troubleshooting
 ms.topic: troubleshooting
@@ -9,29 +9,31 @@ author: bpinto
 ms.author: bpinto
 ---
 
-# Troubleshoot BareMetal Machine Provisioning in Nexus Cluster
+# Troubleshoot BMM provisioning in Azure Operator Nexus cluster
 
-As part of Cluster deploy action, BareMetal machines (BMM) are provisioned with required roles to participate in the Nexus Cluster. This document supports troubleshooting for common provisioning issues using Azure CLI, Azure Portal, and the server Baseboard Management Controller (BMC). For the Operator Nexus Platform, the underlying Dell server hardware uses Integrated Dell Remote Access Controller (iDRAC) as the BMC.
+As part of cluster deploy action, bare metal machines (BMM) are provisioned with required roles to participate in the cluster. This document supports troubleshooting for common provisioning issues using Azure CLI, Azure portal, and the server baseboard management controller (BMC). For the Azure Operator Nexus platform, the underlying server hardware uses integrated Dell remote access controller (iDRAC) as the BMC.
 
 ## Prerequisites
 1. Install the latest version of the [appropriate CLI extensions](howto-install-cli-extensions.md)
 2. Gather the following information:
-  - Subscription ID (SUBSCRIPTION)
-  - Cluster name (CLUSTER), Resource Group (CLUSTER_RG), and Managed Resource Group (CLUSTER_MRG)
-3. The user needs access to the subscription to run Nexus Network Fabric (NF) and Network Cloud (NC) CLI extension commands
+   - Subscription ID (SUBSCRIPTION)
+   - Cluster name (CLUSTER)
+   - Resource group (CLUSTER_RG)
+   - Managed resource group (CLUSTER_MRG)
+3. The user needs access to the subscription to run Azure Operator Nexus network fabric (NF) and network cloud (NC) CLI extension commands
 4. Log in to Azure CLI and select the subscription where the cluster is deployed
 
 ## BMM roles
-For a given SKU, there are required roles to manage and operate the underlying Kubernetes cluster.
+For a given SKU, there are required roles to manage and operate the underlying kubernetes cluster.
 
-The following roles are assigned to BMM resources (see [BMM Roles](reference-near-edge-baremetal-machine-roles.md)):
+The following roles are assigned to BMM resources (see [BMM roles reference](reference-near-edge-baremetal-machine-roles.md)):
 
-  - `Control plane`: BMM responsible for running the Kubernetes control plane agents for Nexus platform cluster.
-  - `Management plane`: BMM responsible for running the Nexus platform agents including controllers and extensions.
-  - `Compute plane`: BMM responsible for running actual tenant workloads including Nexus Kubernetes Clusters and Virtual Machines.
+  - `Control plane`: BMM responsible for running the kubernetes control plane agents for cluster.
+  - `Management plane`: BMM responsible for running the platform agents including controllers and extensions.
+  - `Compute plane`: BMM responsible for running actual tenant workloads including kubernetes clusters and virtual machines.
 
-## Listing BareMetal Machine status
-This command will `list` all `bareMetalMachineName` resources in the Managed Resource Group with simple status:
+## Listing BMM status
+This command will `list` all `bareMetalMachineName` resources in the managed resource group with simple status:
 
 ```azurecli
 az networkcloud baremetalmachine list -g $CLUSTER_MRG -o table
@@ -41,19 +43,20 @@ Name          ResourceGroup                  DetailedStatus    DetailedStatusMes
 BMM_NAME      CLUSTER_MRG                    STATUS            STATUS_MSG
 ```
 
-Where `STATUS` goes through the following phases through the BareMetal Machine provisioning process (see [BMM Status in Azure Operator Nexus Compute Concepts](concepts-compute.md)):
+Where `STATUS` goes through the following phases through the BMM provisioning process (see [BMM Status in Azure Operator Nexus Compute Concepts](concepts-compute.md)):
 
 `Registering` -> `Preparing` -> `Inspecting` -> `Available` -> `Provisioning` -> `Provisioned`
 
 These phases are defined as follows:
+
 | Phase | Definition |
 | --- | --- |
-| `Registering` | Verify BMC Connectivity and BMC Credentials, Add BMM to Provisioning Service |
+| `Registering` | Verify BMC connectivity and BMC credentials, add BMM to provisioning service |
 | `Preparing` | Reboot BMM, reset BMC, verify power state |
-| `Inspecting` | Update firmware, apply BIOS settings, and configure RAID |
+| `Inspecting` | Update firmware, apply BIOS settings, and configure storage |
 | `Available` | BMM ready to install OS |
-| `Provisioning` | OS image installing on the BMM, BMM attempts to join Cluster |
-| `Provisioned` | BMM successfully provisioned and joined Cluster |
+| `Provisioning` | OS image installing on the BMM and attempts to join cluster |
+| `Provisioned` | BMM successfully provisioned and joined to cluster |
 | `Deprovisioning` | BMM provisioning failed and retrying |
 | `Failed` | BMM provisioning failed and requires recovery action, all retries exhausted |
 
@@ -72,29 +75,30 @@ BMM_NAME        RSTATE        PROV_STATE           STATUS            STATUS_MSG
 ```
 
 Where the output is defined as follows:
+
 | Output | Definition |
 | --- | --- |
-| BMM_NAME | BareMetal Machine Name |
-| RSTATE | Cluster Participation Status (`True`,`False`) |
-| PROV_STATE | Provisioning State (`Succeeded`,`Failed`) |
-| STATUS | Provisioning Detailed Status (`Registering`,`Preparing`,`Inspecting`,`Available`,`Provisioning`,`Provisioned`,`Deprovisioning`,`Failed`) |
-| STATUS_MSG | Detailed Provisioning Status Message |
-| POWER_STATE | Power State of BMM (`On`,`Off`) |
-| BMM_ROLE | BMM Cluster Role contains (`control-plane`,`management-plane`,`compute-plane`) |
-| CREATE_DATE | BMM Creation Date |
+| BMM_NAME | BMM name |
+| RSTATE | Cluster participation status (`True`,`False`) |
+| PROV_STATE | Provisioning state (`Succeeded`,`Failed`) |
+| STATUS | Provisioning detailed status (`Registering`,`Preparing`,`Inspecting`,`Available`,`Provisioning`,`Provisioned`,`Deprovisioning`,`Failed`) |
+| STATUS_MSG | Detailed provisioning status message |
+| POWER_STATE | Power state of BMM (`On`,`Off`) |
+| BMM_ROLE | BMM cluster role contains (`control-plane`,`management-plane`,`compute-plane`) |
+| CREATE_DATE | BMM creation date |
 
 For example:
 ```azurecli
 x01dev01c01w01  True          Succeeded            Provisioned       The OS is provisioned to the machine       On            platform.afo-nc.microsoft.com/compute-plane=true  2024-05-03T15:12:48.0934793Z
 x01dev01c01w01  False         Failed               Preparing         Preparing for provisioning of the machine  Off           platform.afo-nc.microsoft.com/compute-plane=true  2024-05-03T15:12:48.0934793Z
 ```
 
-## BareMetal Machine details
+## BMM details
 To show details and status of a single BMM:
 ```azurecli
 az networkcloud baremetalmachine show -g $CLUSTER_MRG -n $BMM_NAME
 ```
-For important BareMetal Machine details:
+For additional BMM details used in troubleshooting:
 ```azurecli
 az networkcloud baremetalmachine show -g $CLUSTER_MRG -n $BMM_NAME --query "{name:name,BootMAC:bootMacAddress,BMCMAC:bmcMacAddress,Connect:bmcConnectionString,SN:serialNumber,rackId:rackId,RackSlot:rackSlot}" -o table
 ```
@@ -105,20 +109,18 @@ The following conditions can cause provisioning failures:
 
 | Error Type | Resolution |
 | ---------- | ---------- |
-| BMC shows Backplane Comm | Remote Flea drain, Physical Flea Drain, BareMetal Machine Replace |
-| Preboot eXecution Environment (PXE) MAC Address mismatch | BareMetal Machine Replace |
-| BMC MAC Address mismatch | BareMetal Machine Replace |
-| Boot Network Data not Retrieved from Redfish | Bounce Port, Remote Flea drain, Physical Flea Drain, BareMetal Machine Replace |
-| Disk Data not retrieved from Redfish | Re-seat Disk, Re-seat RAID Controller (PERC), Remote Flea drain, Physical Flea Drain, BareMetal Machine Replace |
-| BMC Unreachable | Bounce Port, Reseat Cable, Remote Flea drain, Physical Flea Drain, BareMetal Machine Replace |
-| BMC fails log in | Update Credentials on BMC, BareMetal Machine Replace |
-| DIMM, CPU, OEM Critical Errors | Resolve Hardware Issue, BareMetal Machine Replace |
-| Stuck at Grub Loader | Reset NVRAM, BareMetal Machine Replace |
-
-### Azure Bare Metal Machine activity log
+| BMC shows `Backplane Comm` critical error | Remote flea drain, physical flea drain, BMM replace action |
+| Boot network data response empty from BMC | Bounce port on fabric device, remote flea drain, physical flea drain, BMM replace action |
+| Disk data response empty from BMC | Reseat disk, re-seat storage controller, remote flea drain, physical flea drain, BMM replace action |
+| BMC unreachable | Bounce port on fabric device, reseat cable, remote flea drain, physical flea drain, BMM replace action |
+| BMC fails log in | Update credentials on BMC, BMM replace action |
+| DIMM, CPU, OEM critical errors | Resolve hardware issue, BMM replace action |
+| Console stuck at grub menu | Reset NVRAM, BMM replace action |
+
+### Azure BMM activity log
 
 1. Log in to [Azure Portal](https://portal.azure.com/).
-2. Search on the BMM Name in the top `Search` box.
+2. Search on the BMM name in the top `Search` box.
 3. Select the `Bare Metal Machine (Operator Nexus)` from the search results.
 4. Select `Activity log` on the left side menu.
 5. Make sure the `Timespan` encompasses the provisioning period.
@@ -128,56 +130,57 @@ The following conditions can cause provisioning failures:
 Look for failures related to invalid credentials or BMC unavailable.
 
 ### Determine BMC IPv4 address
-The IPv4 address of the BMC (BMC_IP) is the `Connect` value returned from the `BareMetal Machine Details` section.
+The IPv4 address of the BMC (BMC_IP) is in the `Connect` value returned from the previous `BMM Details` section.
 
 ### Validate MAC address of BMM against BMC data
 
-To get the MAC address information from the BareMetal Machine:
+To get the MAC address information from the BMM:
 ```azurecli
 az networkcloud baremetalmachine show -g $CLUSTER_MRG -n $BMM_NAME --query "{name:name,BootMAC:bootMacAddress,BMCMAC:bmcMacAddress,SN:serialNumber,rackId:rackId,RackSlot:rackSlot}" -o table
 ```
 
 Verify the MAC address data against the BMC through the WEB UI: 
-`BMC` -> `Dashboard` - Shows BMC MAC Address
-`BMC` -> `System Info` -> `Network` -> `Embedded.1-1-1` - Shows Boot MAC Address
+`BMC` -> `Dashboard` - Shows BMC MAC address
+`BMC` -> `System Info` -> `Network` -> `Embedded.1-1-1` - Shows Boot MAC address
 
-Verify the MAC address using `racadm` from a Jumpbox that has access to the BMC network:
+Verify the MAC address using `racadm` from a jumpbox that has access to the BMC network:
 ```bash
 racadm --nocertwarn -r $IP -u $BMC_USR -p $BMC_PWD getsysinfo | grep "MAC Address "        #BMC MAC
 racadm --nocertwarn -r $IP -u $BMC_USR -p $BMC_PWD getsysinfo | grep "NIC.Embedded.1-1-1"  #Boot MAC
 ```
 
-If the MAC address supplied to the cluster is incorrect, use the BareMetal Machine replace action at [BMM actions](howto-baremetal-functions.md) to correct the addresses.
+If the MAC address supplied to the Cluster is incorrect, use the BMM replace action at [BMM actions](howto-baremetal-functions.md) to correct the addresses.
 
 ### Ping test BMC connectivity
 
 Attempt to run ping against the BMC IPv4 address:
-1. Obtain the IPv4 address (BMC_IP) from `Determine BMC IPv4 Address` above.
+1. Obtain the IPv4 address (BMC_IP) from the previous `Determine BMC IPv4 address`.
 2. Test ping to the BMC:
 
-   To test from a Jumpbox that has access to the BMC network:
+   To test from a jumpbox that has access to the BMC network:
    ```bash 
    ping $BMC_IP -c 3
    ```
 
-   To test from a  BareMetal Machine control-plane host:
+   To test from a BMM control-plane host using Azure CLI:
    ```azurecli
    az networkcloud baremetalmachine run-read-command -g $CLUSTER_MRG -n $BMM_NAME --limit-time-seconds 60 --commands "[{command:'ping',arguments:['$BMC_IP',-c,3]}]"
    ```
 
-### Reset Port on Fabric Device
-If the BMC_IP is not responsive, a reset of the fabric port retriggers autonegotiation on the port and may bring it back online.
+### Reset port on fabric device
+If the BMC_IP is not responsive, a reset of the fabric device port retriggers autonegotiation on the port and may bring it back online.
 
 To find the `Network Fabric` port from Azure:
-1. Obtain the RackID and RackSlot from the previous `BareMetal Machine Details` section.
-2. In `Azure Portal`, drill down to the `Network Rack` RackID for the BareMetal Machine Rack.
-3. Select `Network Devices` tab and the Management (Mgmt) switch for the rack.
-4. Under `Resources`, select `Network Interfaces` and then the interface for the BMC (iDRAC) or Boot (PXE) for the port that requires reset.
+1. Obtain the `RackID` and `RackSlot` from the previous `BMM Details` section.
+2. In `Azure Portal`, drill down to the `Network Rack` RackID for the BMM.
+3. Select `Network Devices` tab and the management (Mgmt) switch for the rack.
+4. Under `Resources`, select `Network Interfaces` and then the BMC (iDRAC) or boot (PXE) interface for the port that requires reset.
 
    Collect the following information:
-   - Network Fabric Resource Group (NF_RG)
-   - Device Name (NF_DEVICE_NAME)
-   - Interface Name (NF_DEVICE_INTERFACE_NAME).
+   - Network fabric resource group (NF_RG)
+   - Device name (NF_DEVICE_NAME)
+   - Interface name (NF_DEVICE_INTERFACE_NAME)
+
 5. Reset the port:
 
    To reset the port using Azure CLI:
@@ -187,36 +190,36 @@ To find the `Network Fabric` port from Azure:
    ```
 
 ### BMM remote power drain (flea drain)
-Perform a remote Flea Drain against the BareMetal Machine through the WEB UI:
+Perform a remote flea drain against the BMM through the BMC UI:
 `BMC` -> `Configuration` -> `BIOS Settings` -> `Miscellaneous Settings` -> `Select "Full Power Cycle" under Power Cycle Request` -> `Apply and reboot`
 
-Perform a remote flea drain using `racadm` from a Jumpbox that has access to the BMC network:
+Perform a remote flea drain using `racadm` from a jumpbox that has access to the BMC network:
 ```bash
 racadm set bios.miscsettings.powercyclerequest FullPowerCycle
 racadm jobqueue create BIOS.Setup.1-1
 racadm serveraction powercycle
 ```
 
 ### BMM physical power drain (flea drain)
-For a physical flea drain, the local site hands physically disconnect the power cables from both power adapters for 5 minutes and then restore power. This process ensures the server, capacitors, and all components have complete power removal and all cached data are cleared.
+For a physical flea drain, the local site hands physically disconnect the power cables from both power adapters for 5 minutes and then restore power. This process ensures the server, capacitors, and all components have complete power removal and all cached data is cleared.
 
 ### Reset NVRAM
-If provisioning failed due to an OEM or hardware error, the boot sequence may be locked in NVRAM to `PXE boot` instead of `hdd` or `hard drive` listed first in the boot order. 
+If provisioning failed due to an OEM or hardware error, the boot sequence may be locked in NVRAM to `PXE boot` instead of showing `hdd` or `hard drive` listed first in the boot order. 
 
-This condition typically shows the BareMetal Machine at the GRUB Bootloader on the console and is blocked without intervention. 
+This condition typically shows the BMM at the bootloader stage on the console and is blocked without manual keystroke intervention. 
 
-To reset the NVRAM, use the following BMC Sequence:
+To reset the NVRAM, use the following sequence in the BMC UI:
 `Maintenance` -> `Diagnostics` -> `Reset iDrac to Factory Defaults` -> `Discard All Settings, but preserve user and network settings` -> `Apply and reboot`
 
 ### Reset BMC password
-If the Activity Log indicates invalid credentials on the BMC, run the following command from a Jumpbox that has access to the BMC network:
+If the activity log indicates invalid credentials on the BMC, run the following command from a jumpbox that has access to the BMC network:
 ```bash
 racadm -r $BMC_IP -u $BMC_USER -p $CURRENT_PASSWORD  set iDRAC.Users.2.Password $BMC_PWD
 ```
 
 ## Adding servers back into the Cluster after a repair
 
-After Hardware is fixed, run BMM Replace following instructions from the following page [BMM actions](howto-baremetal-functions.md).
+After hardware is fixed, run BMM replace action following instructions from the following page [BMM actions](howto-baremetal-functions.md).
 
 If you still have questions, [contact support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
-For more information about Support plans, see [Azure Support plans](https://azure.microsoft.com/support/plans/response/).
+For more information about support plans, see [Azure Support plans](https://azure.microsoft.com/support/plans/response/).