edit pass: azure-operator-nexus-cluster-and-bmm

paulth1 · paulth1 · commit 1fa29cc86133 · 2024-12-04T14:23:19.000-08:00
diff --git a/articles/operator-nexus/troubleshoot-accepted-cluster-hydration.md b/articles/operator-nexus/troubleshoot-accepted-cluster-hydration.md
@@ -1,6 +1,6 @@
 ---
-title: "Azure Operator Nexus: Accepted Cluster"
-description: Learn how to troubleshoot accepted Cluster resources.
+title: "Azure Operator Nexus: Accepted cluster"
+description: Learn how to troubleshoot accepted cluster resources.
 author: matternst7258
 ms.author: matthewernst
 ms.service: azure-operator-nexus
@@ -10,13 +10,13 @@ ms.date: 10/30/2024
 # ms.custom: template-include
 ---
 
-# Troubleshoot accepted Cluster resources
+# Troubleshoot accepted cluster resources
 
-Operator Nexus relies on mirroring, or hydrating, resources from the on-premises cluster to Azure. When this process is interrupted, the Cluster resource can move to the `Accepted` state.
+Azure Operator Nexus relies on mirroring, or hydrating, resources from the on-premises cluster to Azure. When this process is interrupted, the cluster resource can move to the `Accepted` state.
 
 ## Diagnosis
 
-The Cluster status is viewed via the Azure portal or the Azure CLI.
+The cluster status is viewed via the Azure portal or the Azure CLI.
 
 ```bash
 az networkcloud cluster show --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME>
@@ -28,7 +28,7 @@ Follow these steps for mitigation.
 
 ### Trigger the resource sync
 
-1. From the Cluster resource page in the Azure portal, add a tag to the Cluster resource.
+1. From the cluster resource page in the Azure portal, add a tag to the cluster resource.
 1. The resource moves out of the `Accepted` state.
 
 ```bash
@@ -39,16 +39,16 @@ az resource tag --tags exampleTag=exampleValue --name <CLUSTER> --resource-group
 
 ## Verification
 
-After the tag is applied, the Cluster moves to the `Running` state.
+After the tag is applied, the cluster moves to the `Running` state.
 
 ```bash
 az networkcloud cluster show --resource-group <RESOURCE_GROUP> --name <CLUSTER_NAME>
 ```
 
-If the Cluster resource maintains the state after more than five minutes, contact Microsoft support.
+If the cluster resource maintains the state for more than five minutes, contact Microsoft support.
 
 ## Related content
 
 - For more information about how resources are hydrated, see [Azure Arc-enabled Kubernetes](/azure/azure-arc/kubernetes/overview).
-- If you still have questions, [contact Azure support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
+- If you still have questions, contact [Azure 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/).
diff --git a/articles/operator-nexus/troubleshoot-bare-metal-machine-provisioning.md b/articles/operator-nexus/troubleshoot-bare-metal-machine-provisioning.md
@@ -250,5 +250,7 @@ racadm -r $BMC_IP -u $BMC_USER -p $CURRENT_PASSWORD  set iDRAC.Users.2.Password
 
 After the hardware is fixed, run the BMM `replace` action by following the instructions in [Manage the lifecycle of bare metal machines](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/).
+## Related content
+
+- If you still have questions, contact [Azure 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/).
diff --git a/articles/operator-nexus/troubleshoot-control-plane-quorum.md b/articles/operator-nexus/troubleshoot-control-plane-quorum.md
@@ -29,7 +29,7 @@ Follow the steps in this troubleshooting article when multiple control plane nod
 
 ## Procedure
 
-1. Identify the Nexus Management Node:
+1. Identify the Azure Operator Nexus management nodes:
    - To identify the management nodes, run `az networkcloud baremetalmachine list -g <ResourceGroup_Name>`.
    - Sign in to the identified server.
    - Ensure that the ironic-conductor service is present on this node by using `crictl ps -a |grep -i ironic-conductor`. Here's example output:
@@ -39,7 +39,7 @@ Follow the steps in this troubleshooting article when multiple control plane nod
         <id>       <id>       6 hours ago       Running       ironic-conductor       0       <id>
         ~~~
 
-1. Determine the Dell remote access controller (iDRAC) IP of the server:
+1. Determine the integrated Dell remote access controller (iDRAC) IP of the server:
    - Run the command `az networkcloud cluster list -g <RG_Name>`.
    - The output of the command is JSON with the iDRAC IP.
 
@@ -68,5 +68,7 @@ Follow the steps in this troubleshooting article when multiple control plane nod
 
 The servers should now be restored.
 
-If you still have questions, [contact Azure 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/).
+## Related content
+
+- If you still have questions, contact [Azure 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/).
diff --git a/articles/operator-nexus/troubleshoot-hardware-validation-failure.md b/articles/operator-nexus/troubleshoot-hardware-validation-failure.md
@@ -9,7 +9,7 @@ author: vnikolin
 ms.author: vanjanikolin
 ---
 
-# Troubleshoot hardware validation failure in a Nexus cluster
+# Troubleshoot hardware validation failure in an Azure Operator Nexus cluster
 
 This article describes how to troubleshoot a failed server hardware validation (HWV). HWV is run as part of a cluster deploy action and a bare metal `replace` action. HWV validates a bare metal machine (BMM) by executing test cases against the baseboard management controller (BMC). The Azure Operator Nexus platform is deployed on Dell servers. Dell servers use the integrated Dell remote access controller (iDRAC), which is the equivalent of a BMC.
 
@@ -480,7 +480,7 @@ This section discusses troubleshooting for problems you might encounter.
         }
     ```
 
-    * Allow-listed critical alarms and warning alarms are logged as informational starting with Nexus release 3.14.
+    * Allow-listed critical alarms and warning alarms are logged as informational starting with Azure Operator Nexus release 3.14.
 
     ```yaml
         {
@@ -696,5 +696,7 @@ This section discusses troubleshooting for problems you might encounter.
 
 After the hardware is fixed, run the BMM `replace` action by following the instructions in [Manage the lifecycle of bare metal machines](howto-baremetal-functions.md).
 
-If you still have questions, [contact Azure 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/).
+## Related content
+
+- If you still have questions, contact [Azure 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/).
diff --git a/articles/operator-nexus/troubleshoot-lacp-bonding.md b/articles/operator-nexus/troubleshoot-lacp-bonding.md
@@ -15,7 +15,7 @@ On physical host startup, the two Mellanox cards are bonded to a pair of Arista
 
 ## Diagnosis
 
-If LACP isn't negotiated correctly, traffic loss can occur. But traffic can pass for some flows too. This behavior can manifest itself as a virtual machine that can't get on the network, or even as oam/storage outages.
+If LACP isn't negotiated correctly, traffic loss can occur. But traffic can pass for some flows too. This behavior can manifest itself as a virtual machine that can't get on the network, or even as object attribute memory (OAM) or storage outages.
 
 ## Check LACP bonding
 
@@ -48,5 +48,5 @@ The most common causes for these LACP issues are host or switch miswiring or mis
 
 ## Related content
 
-- If you still have questions, [contact Azure support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
+- If you still have questions, contact [Azure 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/).
diff --git a/articles/operator-nexus/troubleshoot-memory-limits.md b/articles/operator-nexus/troubleshoot-memory-limits.md
@@ -15,7 +15,7 @@ Learn about troubleshooting for container memory limits in this article.
 
 ## Alerts for memory limits
 
-We recommend that you have alerts set up for the Operator Nexus cluster to look for Kubernetes pods that restart from `OOMKill` errors. These alerts let you know if a component on a server is working appropriately.
+We recommend that you have alerts set up for the Azure Operator Nexus cluster to look for Kubernetes pods that restart from `OOMKill` errors. These alerts let you know if a component on a server is working appropriately.
 
 The following table lists the metrics that are exposed to identify memory limits.
 
