More changes

alkohli · alkohli · commit 60cf256a4071 · 2024-08-21T10:30:57.000-07:00
diff --git a/azure-stack/hci/manage/troubleshoot-deployment.md b/azure-stack/hci/manage/troubleshoot-deployment.md
@@ -10,11 +10,11 @@ ms.date: 08/21/2024
 
 # Troubleshoot Azure portal deployment validation issues for Azure Stack HCI, version 23H2
 
-[!INCLUDE [hci-applies-to-23h2](../../includes/hci-applies-to-23h2.md)]
+> Applies to: Azure Stack HCI, version 23H2 running 2405 or later
 
 This article provides guidance on how to troubleshoot deployment validation issues experienced during the deployment of your Azure Stack HCI cluster via the Azure portal.
 
-## Error - deployment vaildation failure 
+## Error - deployment validation failure
 
 When deploying Azure Stack HCI, version 23H2 via the Azure portal, you might encounter a deployment validation failure.
 The "Azure Stack HCI Network - Check network requirements" validation task fail with the following error:
@@ -30,17 +30,17 @@ Example: 192.168.0.1 or 192.168.0.1","Target":null,"Details":null}].
 If you go to the **Networking** tab in Azure portal deployment, within the **Network Intent** configuration, you could see the following error:
 
 ```
-The selected physical network adapter is not binded to the management virtual Switch.
+The selected physical network adapter is not binded to the management virtual switch.
 ```
 
 ## Cause
 
-This issue occurs on deployments triggered after August 6th. The issue only happens if the deployment validation was triggered on the cluster and the validation result was a failure, with subsequent validation retries.
+This issue occurs on deployments triggered after August 6. The issue only happens if the deployment validation was triggered on the cluster and the validation result was a failure, with subsequent validation retries.
 
 The issue occurs for the following reason:
 
 - Validation on the device creates a VM switch for network related tests and is deleted at the end of tests.
-- `DeviceManagementExtension` extension is not detecting the deletion of the VM switch.
+- `DeviceManagementExtension` extension isn't detecting the deletion of the VM switch.
 
 ## Recommended resolution
 
@@ -53,25 +53,25 @@ The multi-step resolution process includes the following steps:
 - [Redo the Azure portal](#redo-the-azure-portal)
 - [Recreate the lock on the seed node resource](#recreate-the-lock-on-the-seed-node-resource)
 
-### Remove the lock from the seed node
-
 > [!NOTE]
-> All the steps in this section need to be performed on the seed node.
+> All the steps in this article need to be performed on the seed node.
+
+### Remove the lock from the seed node
 
-Follow this multi-step process to mitigate this validation error:
+Follow these steps to remove the lock from the seed node:
 
 1. To remove the lock, in the Azure portal, go to the object via the resource group or within Machines - Azure Arc.  
 1. In the left-pane, go to **Settings > Locks**.  You should see a lock named **DoNotDelete**. This is the automatic resource lock that is created when the node is onboarded.
 1. Select **Delete** against the lock.
 
-If you attmept the steps in the next section without removing the lock, the **Delete** command fails with the following error:
+If you attempt the steps in the next section without removing the lock, the **Delete** command fails with the following error:
 
 ```
 Some resources failed to be deleted (run with `--verbose` for more information):
 /subscriptions/<subid>/resourceGroups/<rgname>/providers/Microsoft.HybridCompute/machines/<machinename>/providers/Microsoft.AzureStackHCI/edgeDevices/default
 ```
 
-Here is the example output when run with the `--verbose` switch:
+Here's the example output when run with the `--verbose` switch:
 
 ```Output
 (ScopeLocked) The scope '/subscriptions/<subid>/resourceGroups/<rgname>/providers/Microsoft.HybridCompute/machines/<machinename>/providers/Microsoft.AzureStackHCI/edgeDevices/default' cannot perform delete operation because following scope(s) are locked: '/subscriptions/<subid>/resourceGroups/<rgname>/providers/Microsoft.HybridCompute/machines/<machinename>'. Please remove the lock and try again.
@@ -85,7 +85,7 @@ With the lock removed, follow these steps to remove the validation error.
 
 1. Connect to the seed node. Run the following PowerShell command:
 
-    ```powershell
+    ```PowerShell
     Get-VMSwitch
     ```
 
@@ -97,7 +97,7 @@ With the lock removed, follow these steps to remove the validation error.
     Remove-VMSwitch -Name "<VM Switch Name>" -Force
     ```
 
-    Make sure to use the VM switch name from the `Get-VMSwitch` command. If you didn't intentionally create a VM switch, the `Get-VMSwitch` command will have no results. The failure occurs because the Network Validation Step cleaned up the VM switch, but the `DeviceManagementExtension` didn't detect the cleanup.
+    Make sure to use the VM switch name from the `Get-VMSwitch` command. If you didn't intentionally create a VM switch, the `Get-VMSwitch` command has no results. The failure occurs because the Network Validation Step cleaned up the VM switch, but the `DeviceManagementExtension` didn't detect the cleanup.
 
 1. Confirm the device cleanup and wait for the cleanup to complete.
 
@@ -107,7 +107,7 @@ After the VM switch on the device is removed, clean up the Edge Device ARM resou
 
 1. On a client that can access to Azure, verify install or install AZ CLI: [Install Azure CLI on Windows](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?tabs=azure-cli)
    - You can verify install by running: `az`
-   - If installed, this will output a `"Welcome to Azure CLI!"` message with available commands.
+   - If installed, this outputs a `"Welcome to Azure CLI!"` message with available commands.
 
 1. Sign in to Azure with az cli. Run the following command:
     
@@ -119,48 +119,52 @@ After the VM switch on the device is removed, clean up the Edge Device ARM resou
    
 1. To set a specific subscription, run the following command:
 
-    ```azurecli
+    ```AzureCLI
     az account set --subscription "<subGUID>"
     ```
 
     Replace the value in the above example command with the appropriate value for `<subGUID>`.
-1. Output the data stored within the `edgeDevices` resource that has the incorrectly stored VM Switch information with the following command:
+1. Output the data stored within the `edgeDevices` resource that has the incorrectly stored VM Switch information. Run the following command:
 
-    ```azurecli
+    ```AzureCLI
     az resource show --ids "/subscriptions/<subGUID>/resourceGroups/<resourceGROUPNAME>/providers/Microsoft.HybridCompute/machines/<machineNAME>/providers/Microsoft.AzureStackHCI/edgeDevices/default"
     ```
 
     Replace the values in the above example command with the appropriate values for:`<subGUID>`, `<resourceGROUPNAME>`, and `<machineNAME>`.
     
-    Here is an example output:
+    Here's an example output:
     
     ```output
     az resource show --ids "/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HybridCompute/machines/ASRR1N26R15U33/providers/Microsoft.AzureStackHCI/edgeDevices/default"
     ```
 
-    The output of this command will show quite a bit of detail about the <machineNAME> used in the command. Near the bottom of the output, you will see a section for `"switchDetails"`, which will more than likely show the following (which is the Validation VM Switch that was created and cleaned up on the device, but was not detected by the DeviceManagementExtension and updated cloud-side):
+    The output of this command shows quite a bit of detail about the <machineNAME> used in the command. Near the bottom of the output, there is a section for `"switchDetails"`, which will more than likely show the following (which is the Validation VM Switch that was created and cleaned up on the device, but wasn't detected by the DeviceManagementExtension and updated cloud-side):
     `"switchName": "ConvergedSwitch(managementcompute)",`
     `"switchType": "External"`
 
 1. After confirming the `show` command worked by outputting the `edgeDevices` data, and likely confirming the `"switchDetails"`, it is time to `delete` the resource from ARM so it can be refreshed appropriately from the device.
 
-1. Delete the `edgeDevices` resource which has the incorrectly stored VM Switch information with the following command:
-    `az resource delete --ids "/subscriptions/<subGUID>/resourceGroups/<resourceGROUPNAME>/providers/Microsoft.HybridCompute/machines/<machineNAME>/providers/Microsoft.AzureStackHCI/edgeDevices/default"`
+1. Delete the `edgeDevices` resource, which has the incorrectly stored VM switch information. Run the following command:
+
+    ```AzureCLI
+    az resource delete --ids "/subscriptions/<subGUID>/resourceGroups/<resourceGROUPNAME>/providers/Microsoft.HybridCompute/machines/<machineNAME>/providers/Microsoft.AzureStackHCI/edgeDevices/default"
+    ```
     
-    Replace the values (remember to remove the "<>" characters as well) in the above example command with the appropriate values for:
+    Replace the values (remember to remove the \<\> characters as well) with the appropriate values for:
       `<subGUID>`
       `<resourceGROUPNAME>`
       `<machineNAME>`
     
-    This is the same resource `--ids` from the `show`, so you can just leverage that same string. In fact, you could just "up arrow" in the console and replace `show` with `delete`.
+    This is the same resource `--ids` from the `show`, so you can just use that same string. In fact, you could just "up arrow" in the console and replace `show` with `delete`.
 
-    Here is an example output: 
+    Here's an example output:
 
     ```Output
     `az resource delete --ids "/subscriptions/d41eb627-825d-4419-a14d-c6ad485f4110/resourceGroups/EDGECI-REGISTRATION-rr1n26r1512-kXOKQuGV/providers/Microsoft.HybridCompute/machines/ASRR1N26R15U33/providers/Microsoft.AzureStackHCI/edgeDevices/default"
     ```
-    - **Note:** Run just like this, there will be no output from this command, it will either work and return the command prompt, or present an error. It should not present an error, if it does, that will require additional troubleshooting.
-1. Verify the deletion of the resource by running the `show` command again. Here is an example output:
+    When run, there is no output from this command. The command works and returns the command prompt, or presents an error. It shouldn't present an error, if it does, that will require more troubleshooting.
+
+1. Verify the deletion of the resource by running the `show` command again. Here's an example output:
 
     ```Output
     (ResourceNotFound) The resource 'Microsoft.HybridCompute/machines/<machineNAME>/providers/Microsoft.AzureStackHCI/edgeDevices/default' could not be found.
@@ -176,7 +180,7 @@ Follow these steps to refresh the cloud data:
 
 1. Restart the `DeviceManagementService` on the seed node. Run the following PowerShell command:
 
-   ```powershell
+   ```PowerShell
     Restart-Service DeviceManagementService
     ```
 
@@ -187,7 +191,7 @@ Follow these steps to refresh the cloud data:
 
 ### Redo the Azure portal
 
-With device and cloud data now back in sync, you can go to the Azure portal and provide the deployment inputs. The previous step prevents any cached information from previous attempts. 
+With device and cloud data now back in sync, you can go to the Azure portal and provide the deployment inputs. The previous step prevents any cached information from previous attempts.
 
 Follow these steps in the Azure portal:
   
@@ -199,7 +203,7 @@ Follow these steps in the Azure portal:
 
 1. Confirm the information on the subsequent pages. You should see the following changes:
     - On the **Networking** page, you should no longer see the `The selected physical network adapter is not binded to the management virtual Switch` error that might have been seen previously.
-    - On the **Validation** page at the end, if you are past the original issue, the `deploymentdata.physicalnodes[0].ipv4address is not a valid IPv4 address` error won't be displayed.
+    - On the **Validation** page at the end, if you're past the original issue, the `deploymentdata.physicalnodes[0].ipv4address is not a valid IPv4 address` error won't be displayed.
 
 1. If no other validation issues occur, start the deployment.
 
