You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AKS-Arc/aks-arc-diagnostic-checker.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to diagnose common causes for failures in AKS Arc.
4
4
ms.topic: troubleshooting
5
5
author: sethmanheim
6
6
ms.author: sethm
7
-
ms.date: 01/30/2025
7
+
ms.date: 06/27/2025
8
8
ms.reviewer: abha
9
9
10
10
#Customer intent: As an AKS user, I want to use the diagnostic checker to run diagnostic checks on my AKS cluster to find out common causes for AKS cluster create failure.
@@ -13,14 +13,14 @@ ms.reviewer: abha
13
13
14
14
# Use the diagnostic checker to diagnose and fix environment issues for AKS cluster creation failure (preview)
15
15
16
-
It can be difficult to identify environment-related issues, such as networking configurations, that can result in an AKS cluster creation failure. The diagnostic checker is a PowerShell-based tool that can help you identify AKS cluster creation failures due to potential issues in the environment.
16
+
It can be difficult to identify environment-related issues, such as networking configuration, that can result in an AKS cluster creation failure. The diagnostic checker is a PowerShell tool that can help you identify AKS cluster creation failures due to potential issues in the environment.
17
17
18
18
> [!NOTE]
19
-
> You can only use the diagnostic checker tool if an AKS cluster was created, but is in a failed state. You can't use the tool if you don't see an AKS cluster on the Azure portal. If the AKS cluster creation fails before an Azure Resource Manager resource is created, [file a support request](aks-troubleshoot.md#open-a-support-request).
19
+
> You can only use the diagnostic checker tool if an AKS cluster was created, but is in a failed state. You can't use the tool if you don't see an AKS cluster on the Azure portal. If the AKS cluster creation fails before an Azure Resource Manager resource is created, [file a support request](help-support.md).
20
20
21
21
## Before you begin
22
22
23
-
Before you begin, make sure you have the following prerequisites. If you don't meet the requirements for running the diagnostic checker tool, [file a support request](aks-troubleshoot.md#open-a-support-request):
23
+
Before you begin, make sure you have the following prerequisites. If you don't meet the requirements for running the diagnostic checker tool, [file a support request](help-support.md):
24
24
25
25
- Direct access to the Azure Local cluster where you created the AKS cluster. This access can be through remote desktop (RDP), or you can also sign in to one of the Azure Local physical nodes.
26
26
- Review the [networking concepts for creating an AKS cluster](aks-hci-network-system-requirements.md) and the [AKS cluster architecture](cluster-architecture.md).
If you don't see a control plane VM as shown in the previous output, [file a support request](aks-troubleshoot.md#open-a-support-request).
46
+
If you don't see a control plane VM as shown in the previous output, [file a support request](help-support.md).
47
47
48
48
If you see a control plane VM, and it has:
49
49
50
-
- 0 IPv4 addresses: file a [support request](aks-troubleshoot.md#open-a-support-request).
50
+
- 0 IPv4 addresses: file a [support request](help-support.md).
51
51
- 1 IP address: use the IPv4 address as the input for `vmIP` parameter.
52
52
- 2 IP addresses: use any one of the IPv4 address as an input for `vmIP` parameter in the diagnostic checker.
53
53
54
54
## Run the diagnostic checker script
55
55
56
-
Copy the following PowerShell script `run_diagnostic.ps1` into any one node of your Azure Local cluster:
56
+
Copy the following PowerShell script named `run_diagnostic.ps1` into any one node of your Azure Local cluster:
57
57
58
58
```powershell
59
59
<#
@@ -288,4 +288,4 @@ The following table provides a summary of each test performed by the script, inc
288
288
289
289
## Next steps
290
290
291
-
If the problem persists, collect [AKS cluster logs](get-on-demand-logs.md) before you [create a support request](aks-troubleshoot.md#open-a-support-request).
291
+
If the problem persists, collect [AKS cluster logs](get-on-demand-logs.md) before you [create a support request](help-support.md).
0 commit comments