Merge pull request #15694 from MicrosoftDocs/main

8/19/2024 PM Publish

Author: Taojunshen

AKS-Hybrid/aks-edge-howto-setup-machine.md

@@ -4,7 +4,7 @@ description: Learn how to prepare your machines for AKS Edge Essentials clusters
 author: rcheeran
 ms.author: rcheeran
 ms.topic: how-to
-ms.date: 02/13/2024
+ms.date: 08/19/2024
 ms.custom: template-how-to
 ---
 
@@ -111,6 +111,5 @@ This command displays output similar to the following list:
 
 ## Next steps
 
-- Create a [simple deployment](aks-edge-howto-single-node-deployment.md)
-- Create a [full deployment](aks-edge-howto-multi-node-deployment.md)
-
+- [Create a single machine deployment](aks-edge-howto-single-node-deployment.md)
+- [Create a full Kubernetes deployment](aks-edge-howto-multi-node-deployment.md)

azure-stack/hci/concepts/physical-network-requirements.md

@@ -220,7 +220,21 @@ If your switch isn't included, contact your switch vendor to ensure that your sw
 > [!NOTE]
 > Guest RDMA requires both Compute (Standard) and Storage.
 
----
+# [SuperMicro](#tab/SuperMicro)
+### 23H2
+
+|Model |Firmware| Management | Storage | Compute (Standard)| Compute (SDN)|
+|-----  |---| :-:  | :-:  | :-:   | :-:   |
+| [SSE-C4632](https://www.supermicro.com/datasheet/datasheet_SSE-C4632.pdf) <br>(10, 25, 100 GbE)|Broadcom Advanced Enterprise SONiC OS 4.2.1 or later |&check;| &check;| &check;| &check; |
+> [!NOTE]
+> Guest RDMA requires both Compute (Standard) and Storage.
+### 22H2
+
+|Model |Firmware| Management | Storage | Compute (Standard)| Compute (SDN)|
+|-----  |---| :-:  | :-:  | :-:   | :-:   |
+| [SSE-C4632](https://www.supermicro.com/datasheet/datasheet_SSE-C4632.pdf) <br>(10, 25, 100 GbE)|Broadcom Advanced Enterprise SONiC OS 4.2.1 or later |&check;| &check;| &check;| &check; |
+> [!NOTE]
+> Guest RDMA requires both Compute (Standard) and Storage.
 
 ---
 

azure-stack/hci/manage/collect-log-files-arc-enabled-vms.md

@@ -0,0 +1,89 @@
+---
+title: Collect log files for Azure Arc VM on Azure Stack HCI
+description: Learn how to collect log files for an Azure Arc VM on your Azure Stack HCI system. 
+author: alkohli
+ms.topic: how-to
+ms.date: 08/16/2024
+ms.author: alkohli
+ms.reviewer: vlakshmanan
+---
+
+# Collect log files for Azure Arc VM on your Azure Stack HCI system
+
+[!INCLUDE [hci-applies-to-23h2](../../includes/hci-applies-to-23h2.md)]
+
+Collect logs and other files to identify and troubleshoot issues with Arc virtual machines (VMs) in your Azure Stack HCI system.
+
+## Collect files when VM provisioning fails
+
+ Use these files to gather key information about a VM provisioning failure before you contact Microsoft Support for more help.
+
+### Windows VMs
+
+The Windows Panther folder contains Windows setup, installation, and upgrade log files. This folder also includes logs for all scripts used to customize the VM.
+
+| File              | Directory       | Description |
+|-------------------|-----------------|-------------|
+| agent-log-0 | C:\ProgramData\mocguestagent\log\ | Operational logs |
+| SetupAct.log | C:\Windows\panther\ | Contains information about setup actions during the installation. |
+| SetupErr.log | C:\Windows\panther\ | Contains information about setup errors during the installation. |
+| SetupComplete.log | C:\Windows\panther\ | Contains custom scripts that run during or after the Windows Setup process. For HCI, includes enabling WinRM, enabling ssh, and installing Microsoft On-premises Cloud (MOC) guest agent. |
+| Script files | C:\Windows\setup\scripts\ | Scripts from ISO |
+| System.evtx | C:\Windows\system32\winevt\logs\ | Windows event logs |
+
+### Linux VMs
+
+Examine these log files to investigate a VM provisioning failure:
+
+| File              | Directory       | Description |
+|-------------------|-----------------|-------------|
+| cloud-init-output.log | /var/log/ | Captures the output from each stage of cloud-init when it runs. |
+| cloud-init.log | /var/log/ | A detailed log with debugging output, detailing each action taken. |
+| log files | /run/cloud-init/ | Contains logs about how cloud-init decided to enable or disable itself, and what platforms/datasources were detected. These logs are most useful when trying to determine what cloud-init ran or didn't run. |
+
+## Collect guest logs
+
+Collect guest logs to gather information on Arc VM issues before you contact Microsoft Support.
+
+### Logs inside the VM
+
+Windows VM domain join and extension logs:
+
+| File              | Directory       | Description |
+|-------------------|-----------------|-------------|
+| Netsetup.log | C:\Windows\debug\ | Netlogon logs are used for domain join failure. If you don't see  a domain join error, this log is optional. |
+| Extension logs | C:\ProgramData\GuestConfig\extension_logs\ | Extension logs |
+
+For more information, see [Active Directory domain join troubleshooting guidance](/troubleshoot/windows-server/active-directory/active-directory-domain-join-troubleshooting-guidance).
+
+### MOC guest agent logs
+
+MOC guest agent logs are useful when Arc VM provisioning fails with the following error:
+
+`Could not establish HyperV connection for VM ID...`
+
+Example error:
+
+`{"code":"moc-operator virtualmachine serviceClient returned an error while reconciling: rpc error: code = Unknown desc = Could not establish HyperV connection for VM ID [E5BF0FC3-DB6D-40AA-BB46-DD94E4E0719A] within [900] seconds, error: [<nil>]","message":"moc-operator virtualmachine serviceClient returned an error while reconciling: rpc error: code = Unknown desc = Could not establish HyperV connection for VM ID [E5BF0FC3-DB6D-40AA-BB46-DD94E4E0719A] within [900] seconds, error: [<nil>]","additionalInfo":[{"type":"ErrorInfo","info":{"category":"Uncategorized","recommendedAction":"","troubleshootingURL":""}}]}`
+
+#### Windows VMs
+
+Examine these MOC guest agent log files:
+
+| File              | Directory       | Description |
+|-------------------|-----------------|-------------|
+| mocguestagent.log | C:\ProgramData\mocguestagent\log\ | Critical logs |
+| agent-log-0 | C:\ProgramData\mocguestagent\log\ | Operational logs |
+
+#### Linux VMs
+
+Examine these MOC guest agent log files:
+
+| File              | Directory       | Description |
+|-------------------|-----------------|-------------|
+| mocguestagent.service  | sudo journalctl -u | Critical logs |
+| agent-log-0 | /opt/mocguestagent/log/ | Operational logs |
+
+## Next steps
+
+- [Collect logs](./collect-logs.md).

azure-stack/hci/manage/troubleshoot-arc-enabled-vms.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Arc VM management
 description: Learn how to troubleshoot Azure Arc VM management
 author: alkohli
 ms.topic: how-to
-ms.date: 07/10/2024
+ms.date: 07/26/2024
 ms.author: alkohli
 ms.reviewer: vlakshmanan
 ---
@@ -14,46 +14,17 @@ ms.reviewer: vlakshmanan
 
 This article provides guidance on how to collect logs and troubleshoot issues with Azure Arc virtual machines (VMs) in your Azure Stack HCI cluster. It also lists the limitations and known issues that currently exist with Azure Arc VM management.
 
-
-## Collect logs
-
-You can collect logs to identify and troubleshoot issues with Arc VMs in your Azure Stack HCI system. Use these logs to gather key information before you contact Microsoft support for additional help.
-
-Make sure you have the latest PowerShell module for log collection. To update the PowerShell module, run the following command:
-
-```PowerShell
-#Update the PowerShell module
-Install-Module -Name ArcHci -Force -Confirm:$false -SkipPublisherCheck -AcceptLicense
-```
-
-To collect logs for Arc VMs in your Azure Stack HCI cluster, run the following command:
-
-```PowerShell
-$csv_path="<input-from-admin>"
-$VMIP_1="<input-from-admin>"
-az login --use-device-code
-Get-ArcHCILogs -workDirectory $csv_path\ResourceBridge -kvaTokenPath $csv_path\ResourceBridge\kvatoken.tok -ip $VMIP_1
-```
-
-Where:
-
-- **$csv_path** is the full path of the cluster shared volume provided for creating Arc Resource Bridge.
-
-- **$VMIP_1** is the IP address of the Arc Resource Bridge VM.
-
-- Optionally, set the `-logDir` parameter to specify the path to the directory where the generated logs are stored. If you don't specify the path or the parameter, by default the logs are stored in your current working directory.
-
 ## Troubleshoot Azure Arc VMs
 
 This section describes the errors related to Azure Arc VM management and their recommended resolutions.
 
-### Failure when trying to enable guest management
+## Failure when trying to enable guest management
 
 When trying to run the command to enable guest management, you see the following error:
 
 **Error:** `Deployment failed. Correlation ID: 5d0c4921-78e0-4493-af16-dffee5cbf9d8. VM Spec validation failed for guest agent provisioning: Invalid managed identity. A system-assigned managed identity must be enabled in parent resource: Invalid Configuration`
 
-The above failure is because the managed identity wasn't created for this VM. System-assigned Managed Identity is required to enable guest management.
+This failure is because the managed identity wasn't created for this VM. System-assigned Managed Identity is required to enable guest management.
 
 **Resolution:**  
 
@@ -104,13 +75,13 @@ Follow these steps to verify that the Managed Identity isn't created for this VM
 
     :::image type="content" source="./media/troubleshoot-arc-enabled-vms/managed-identity-missing-3.png" alt-text="Screenshot of JSON view when Managed Identity is enabled." lightbox="./media/troubleshoot-arc-enabled-vms/managed-identity-missing-3.png":::  
 
-### Failure deploying an Arc VM
+## Failure deploying an Arc VM
 
 You see the following error when trying to deploy an Arc VM on your Azure Stack HCI cluster:
 
 **Error:** `{"code":"ConflictingOperation","message":"Unable to process request 'Microsoft.AzureStackHCI/virtualMachineInstances'. There is already a previous running operation for resource '/subscriptions/<subscription ID>/resourceGroups/<Resource group name>/providers/Microsoft.HybridCompute/machines/<VM name>/providers/Microsoft.AzureStackHCI/virtualMachineInstances/default'. Please wait for the previous operation to complete."}`
 
-The above failure is because the `SystemAssigned` managed identity object isn't under the `Microsoft.HybridCompute/machines` resource type.
+This failure is because the `SystemAssigned` managed identity object isn't under the `Microsoft.HybridCompute/machines` resource type.
 
 **Resolution:**  
 
@@ -120,7 +91,7 @@ The `SystemAssigned` managed identity object is under `Microsoft.HybridCompute/m
 
 The deployment template should match the provided sample template. For more information, see the sample template in [Create Arc virtual machines on Azure Stack HCI](./create-arc-virtual-machines.md).
 
-### Failure deleting storage path
+## Failure deleting storage path
 
 When trying to delete a storage path on your Azure Stack HCI cluster, you might see an error similar to the following message. Resource numbers and versions may vary in your scenario.
 
@@ -140,7 +111,7 @@ Follow these steps before trying to remove a storage path:
 1. Remove the associated workloads and the images present on the storage path you want to delete. Look for the following prefixes on the image names: `linux-cblmariner`, `windows-windows2019`, `windows-windows2022`, `windows_k8s`, `aks-image-merged`, `linux-K8s`.
 1. File a [support ticket in the Azure portal](/azure/azure-portal/supportability/how-to-create-azure-support-request).
 
-### Azure CLI installation isn't recognized
+## Azure CLI installation isn't recognized
 
 If your environment fails to recognize Azure CLI after installing it, run the following code block to add the Azure CLI installation path to the environment path.
 

azure-stack/hci/toc.yml

@@ -291,6 +291,8 @@ items:
       - name: Extended Security Updates (ESUs)
         href: manage/azure-benefits-esu.md
 
+    - name: Collect log files for Azure Arc VM
+      href: manage/collect-log-files-arc-enabled-vms.md 
     - name: Troubleshoot
       href: manage/troubleshoot-arc-enabled-vms.md
     - name: FAQs

azure-stack/hci/upgrade/install-solution-upgrade.md

@@ -120,3 +120,15 @@ Follow these steps to verify that the upgrade was successful:
     Here is a screenshot of the resources in the resource group:
 
     :::image type="content" source="./media/install-solution-upgrade/verify-upgrade-portal.png" alt-text="Screenshot of Upgrade Azure Stack HCI resource health." lightbox="./media/install-solution-upgrade/verify-upgrade-portal.png":::
+
+## Post solution upgrade tasks
+
+After the solution upgrade is complete, you may need to perform additional tasks to secure your system and ensure it's ready for workloads. 
+
+- You may need to connect to the system via Remote Desktop Protocol (RDP) to deploy workloads. For more information, see [Enable RDP](../deploy/deploy-via-portal.md#enable-rdp).
+- To prevent the accidental deletion of resources, you can lock resources. We recommend that you lock the Arc Resource Bridge. For more information, see [Lock Arc Resource Bridge](../deploy/deploy-via-portal.md#lock-arc-resource-bridge).
+- You may need to create workloads and storage paths for each volume. For details, see [Create volumes on Azure Stack HCI](../manage/create-volumes.md) and [Create storage path for Azure Stack HCI](../manage/create-storage-path.md).
+
+## Next steps
+
+If you run into issues during the upgrade process, see [Troubleshoot solution upgrade on Azure Stack HCI](./troubleshoot-upgrade-to-azure-stack-hci-23h2.md).

azure-stack/hci/upgrade/validate-solution-upgrade-readiness.md

@@ -82,7 +82,7 @@ Follow these steps to set up the Environment Checker on a server node of your Az
 1. Install the Environment Checker on the server. Run the following PowerShell command from the PSGallery:
 
    ```powershell
-   Install-Module -Name AzStackHci.EnvironmentChecker -allowclobber
+   Install-Module -Name AzStackHci.EnvironmentChecker -AllowClobber
    ```
 
 ### Run the validation
@@ -98,7 +98,7 @@ Follow these steps to set up the Environment Checker on a server node of your Az
 1. To validate other servers in the cluster, run the following PowerShell command:
 
    ```powershell
-   $PsSession=New-Pssession -computername "MyRemoteMachine"
+   $PsSession=New-Pssession -ComputerName "MyRemoteMachine"
    Invoke-AzStackHciUpgradeValidation -PsSession $PsSession
    ```
 
@@ -159,7 +159,7 @@ $windowsFeature =  @(
                 ) 
 foreach ($feature in $windowsFeature) 
 { 
-install-windowsfeature -name $feature -IncludeAllSubFeature -IncludeManagementTools 
+Install-WindowsFeature -Name $feature -IncludeAllSubFeature -IncludeManagementTools 
 } 
 
 #Install requires optional Windows features 
@@ -223,7 +223,7 @@ $windowsOptionalFeature = @(
             ) 
 foreach ($featureName in $windowsOptionalFeature) 
 { 
-enable-windowsoptionalfeature -featurename $featurename -all -online 
+Enable-WindowsOptionalFeature -FeatureName $featurename -All -Online 
 } 
 ```
 
@@ -234,7 +234,7 @@ Ensure that all the cluster members are up and that the cluster is *Online*. Use
 To verify all members of the cluster are online, run the following PowerShell command:
 
 ```powershell
-Get-ClusterNode -cluster "mycluster" 
+Get-ClusterNode -Cluster "mycluster" 
 ```
 
 ## Remediation 3: Suspend BitLocker
@@ -295,7 +295,7 @@ Follow these steps to confirm the storage pool configuration:
 1. To confirm the storage pool size and allocated size, run the following PowerShell command:
 
    ```powershell
-   Get-storagepool -IsPrimordial $false
+   Get-StoragePool -IsPrimordial $false
    ```
 
    <details>
@@ -310,7 +310,7 @@ Follow these steps to confirm the storage pool configuration:
 1. To list all volumes in the storage pool, run the following PowerShell command:
 
    ```powershell
-   Get-storagepool -IsPrimordial $false|Get-VirtualDisk
+   Get-StoragePool -IsPrimordial $false | Get-VirtualDisk
    ```
 
    <details>
@@ -341,10 +341,10 @@ Follow these steps to confirm the storage pool configuration:
 1. To convert the volume to thin provisioned, run the following PowerShell command:
 
    ```powershell
-   Set-virtualdisk -FriendlyName TestVolume -ProvisioningType Thin
+   Set-VirtualDisk -FriendlyName TestVolume -ProvisioningType Thin
    ```
 
-1. To convert the volume to thin provisioned, run the following PowerShell command. Make sure you adjust the CSV name to match your system:
+1. To finish the convertion, the volume must be restarted. To do this, run the following PowerShell command. Make sure you adjust the CSV name to match your system:
 
    ```powershell
    Get-ClusterSharedVolume -Name "Cluster Disk 1" | Stop-ClusterResource
@@ -362,7 +362,7 @@ Follow these steps to confirm the storage pool configuration:
 
    | FriendlyName | ResiliencySettingName | FaultDomainRedundancy | OperationalStatus | HealthStatus | Size | FootprintOnPool | StorageEfficiency |
    |--------------|-----------------------|-----------------------|------------------|--------------|------|-----------------|------------------|
-   |ClusterPerformanceHistory | Mirror | 1 | OK | Healthy | 21 GB | 43 GB | 48.84% |
+   | ClusterPerformanceHistory | Mirror | 1 | OK | Healthy | 21 GB | 43 GB | 48.84% |
    | TestVolume | Mirror | 0 | OK | Healthy | 1 TB | 36.5 GB | 98.63% |
    | TestVolume2 | Mirror | 0 | OK | Healthy | 750 GB | 28.5 GB | 98.25% |
 
@@ -404,7 +404,7 @@ Make sure that the cluster functional level and storage pool version are up to d
    $SubscriptionId = "Your Subscription ID"
    Login-AzAccount –UseDeviceAuthentication –tenantid  $tenantid –subscriptionid $SubscriptionId
    Install-module az.connectedmachine
-   New-AzConnectedMachineExtension -Name "AzureEdgeLifecycleManager"  -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME -Location $Region -Publisher "Microsoft.AzureStack.Orchestration" -ExtensionType "LcmController"  -NoWait
+   New-AzConnectedMachineExtension -Name "AzureEdgeLifecycleManager" -ResourceGroupName $ResourceGroup -MachineName $env:COMPUTERNAME -Location $Region -Publisher "Microsoft.AzureStack.Orchestration" -ExtensionType "LcmController" -NoWait
    ```
 
 ## Remediation 10: Check the MOC install state