|
1 | 1 | --- |
2 | 2 | title: Use diagnostic checker to identify common causes for failures (preview) |
3 | | -description: Learn how to diagnose common causes for failures |
| 3 | +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: 06/17/2024 |
| 7 | +ms.date: 01/30/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. |
11 | 11 |
|
12 | 12 | --- |
13 | 13 |
|
14 | | -# Use diagnostic checker to diagnose and fix environment issues for AKS cluster creation failure (preview) |
| 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 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 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. |
17 | 17 |
|
18 | 18 | > [!NOTE] |
19 | 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). |
@@ -280,12 +280,12 @@ http-connectivity-required-url-test Failure Ensure that the logical network IP a |
280 | 280 |
|
281 | 281 | The following table provides a summary of each test performed by the script, including possible causes for failure and recommendations for mitigation: |
282 | 282 |
|
283 | | -| Test Name | Description | Causes for failure | Mitigation Recommendations | |
| 283 | +| Test name | Description | Causes for failure | Mitigation Recommendations | |
284 | 284 | |--------------------------------------|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| |
285 | 285 | | cloud-agent-connectivity-test | Checks whether the DNS server can resolve the MOC cloud agent FQDN and that the cloud agent is reachable from the control plane node VM. The cloud agent is created using one of the IP addresses from the [management IP pool](/azure-stack/hci/plan/cloud-deployment-network-considerations#management-ip-pool), on port 55000. The control plane node VM is given IP addresses from the Arc VM logical network. | Logical network IP addresses can't connect to management IP pool addresses due to: <br> - Incorrect DNS server resolution. <br> - Firewall rules. <br> - The logical network is in a different vlan than the management IP pool and there's no cross-vlan connectivity. | Make sure that the logical network IP addresses can connect to all the management IP pool addresses on the required ports. Check the [AKS network port and cross vlan requirements](aks-hci-network-system-requirements.md#network-port-and-cross-vlan-requirements) for a detailed list of ports that need to be opened. | |
286 | 286 | | gateway-icmp-ping-test | Checks whether the gateway specified in the logical network attached to the AKS cluster is reachable from the AKS cluster control plane node VM. | - Gateway is down or unreachable. <br>- Network routing issues between the AKS cluster control plane node VM and the gateway. <br>- Firewall blocking ICMP traffic. | - Ensure the gateway is operational.<br>- Verify routing configurations.<br>- Adjust firewall rules to allow ICMP traffic. | |
287 | 287 | | http-connectivity-required-url-test | Checks whether the required URLs are reachable from the AKS cluster control plane node VM. | - Control plane node VM has no outbound internet access. <br> - Required URLs aren't allowed through the firewall. | Ensure that the logical network IP addresses have outbound internet access. If there's a firewall, ensure that the [AKS required URLs](aks-hci-network-system-requirements.md#firewall-url-exceptions) are accessible from the Arc VM logical network. | |
288 | 288 |
|
289 | 289 | ## Next steps |
290 | 290 |
|
291 | | -If the problem persists, collect [AKS cluster logs](get-on-demand-logs.md) before [creating 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](aks-troubleshoot.md#open-a-support-request). |
0 commit comments