Troubleshoot Azure Stack HCI upgrade

Applies to: Azure Stack HCI, version 23H2

This article describes how to identify and troubleshoot common Azure Stack HCI upgrade issues.

Operating system upgrade

When you Upgrade the OS, you may encounter registration failures or network ATC intent health state issues. This section provides steps to troubleshoot these issues.

Registration failures

Run the following PowerShell command to verify that the cluster is registered with Azure:

Get-AzureStackHci

Here's a sample output:

ClusterStatus :          Clustered
RegistrationStatus :     Registered
RegistrationDate :       8/1/2024 9:15:12 AM
AzureResourceName :      Redmond
AzureResourceUri :       /Subscriptions/<Subscription ID>/resourceGroups/Redmond/providers/Microsoft.AzureStackHCI/clusters/Redmond
ConnectionStatus :       Connected
LastConnected :          8/1/2024 11:30:42 AM
NextSync :
IMDSAttestation :        Disabled
DiagnosticLevel :        Basic
Region :

If RegistrationStatus is Not registered, follow troubleshooting steps in Troubleshoot Azure Stack HCI registration.

Network ATC intent health state

Run the following PowerShell command to verify Network ATC intent health state:

Get-NetIntentStatus

Here's a sample output:

PS C:\Users\administrator.CONTOSO> Get-NetlntentStatus
IntentName:            convergedintent
Host:                  nodel 
IsComputeintentSet:    True
IsHanagementlntentSet: True
IsStoragelntentSet:    True
IsStretchlntentSet:    False
LastUpdated:           08/13/2024 18:01:43
LastSuccess:           08/13/2024 17:25:10
RetryCount:            0
LastConfigApplied:     1
Error:                 PhysicalAdapterNotFound
Progress:              1 of 1
ConfigurationStatus:   Retrying
ProvisioningStatus:    Pending

If the ConfigurationStatus isn't healthy, verify that the VM network adapter name is the same as the network adapter name.

Run the following PowerShell commands to verify that the network adapter name for vManagement matches the VM network adapter name:

Get-NetAdapter

Here's a sample output:

Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed 

----                      --------------------                    ------- ------       ----------             --------- 

Embedded FlexibleLOM ...1 HPE Ethernet 10/25Gb 2-port 640FLR-S...       7 Up           B8-83-03-58-91-88        25 Gbps 

Embedded FlexibleLOM ...2 HPE Ethernet 10/25Gb 2-port 640FLR...#2       6 Up           B8-83-03-58-91-89        25 Gbps 

vSMB(converged#Embedde... Hyper-V Virtual Ethernet Adapter #2          20 Up           00-15-5D-20-40-02        25 Gbps 

vManagement(converged)    Hyper-V Virtual Ethernet Adapter             14 Up           B8-83-03-58-91-88        25 Gbps 

vSMB(converged#Embedde... Hyper-V Virtual Ethernet Adapter #3          24 Up           00-15-5D-20-40-03        25 Gbps 
Get-VmNetworkAdapter -ManagementOS 

Here's a sample output:

Name                                          IsManagementOs VMName SwitchName                 MacAddress   Status IPAddresses 

----                                          -------------- ------ ----------                 ----------   ------ ----------- 

vManagement(converged)                        True                  ConvergedSwitch(converged) B88303589188 {Ok} 

vSMB(converged#Embedded FlexibleLOM 1 Port 1) True                  ConvergedSwitch(converged) 00155D204002 {Ok} 

vSMB(converged#Embedded FlexibleLOM 1 Port 2) True                  ConvergedSwitch(converged) 00155D204003 {Ok} 

Both names must match. If names don't match, run the following PowerShell command to rename the network adapter:

Rename-NetAdapter -Name "badname" -NewName "VMNetworkadapterName"

Run the following PowerShell command to force a network ATC intent update:

Set-NetIntentRetryState -Name "YourIntentName"

Solution upgrade

When you Install the solution upgrade, you may encounter issues. This section describes the location of the solution upgrade and solution validation logs that you can use to troubleshoot upgrade-related issues.

Solution upgrade logs

File Directory Description
FullCloudUpgrade.date.time.log C:\clouddeployment\logs Solution upgrade logs

Solution validation logs

File Directory Description
InvokeCloudUpgradeEnvironmentChecker.date.time.log C:\maslogs\lcmecelitelogs Solution validation logs

Next steps

For detailed remediation for common known issues, check out:

Alternatively, you can: