Skip to content

Commit 7719828

Browse files
authored
Merge pull request #17861 from sethmanheim/aks-tsg56
Add TSG for network validation errors
2 parents 145486a + cb4100e commit 7719828

File tree

2 files changed

+104
-0
lines changed

2 files changed

+104
-0
lines changed

AKS-Arc/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -181,6 +181,8 @@
181181
href: check-vm-sku.md
182182
- name: Connectivity issues with MetalLB
183183
href: load-balancer-issues.md
184+
- name: Troubleshoot general network validation errors
185+
href: network-validation-errors.md
184186
- name: Network validation error due to .local domain
185187
href: network-validation-error-local.md
186188
- name: Reference

AKS-Arc/network-validation-errors.md

Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
---
2+
title: Troubleshoot network validation errors
3+
description: Learn how to troubleshoot general network validation errors in AKS Arc.
4+
author: sethmanheim
5+
ms.author: sethm
6+
ms.topic: troubleshooting
7+
ms.date: 05/07/2025
8+
ms.reviewer: pradwivedi
9+
ms.lastreviewed: 05/06/2025
10+
11+
---
12+
13+
# Troubleshoot network validation errors
14+
15+
This article describes how to identify and resolve various network validation errors you might encounter during cluster creation. The article emphasizes the importance of pre-checks for early issue detection. These errors are detected by pre-checks designed to highlight issues early, allowing for easier resolution before the cluster is created.
16+
17+
The article summarizes error codes, their potential causes, and actionable mitigation steps to help you resolve issues effectively.
18+
19+
## CloudAgentConnectivityError
20+
21+
Error: Network validation failed during cluster creation.
22+
23+
### Description
24+
25+
Detailed message: `Not able to connect to http://cloudagent.contoso.local:50000. Error returned: action failed after 5 attempts: Get "http://cloudagent.contoso.local:50000": dial tcp: lookup http://cloudagent.contoso.local: Temporary failure in name resolution`
26+
27+
The MOC cloud agent is created using one of the IP addresses from the [Management IP pool](/azure/azure-local/plan/cloud-deployment-network-considerations#management-ip-pool) on port 5500 and the control plane node VM is given IP addresses from the Arc VM logical network. This error occurs when the MOC cloud agent is not reachable from the control plane VM, or when the DNS servers specified in the Arc VM logical network are unable to resolve the MOC cloud agent FQDN.
28+
29+
### Causes of failure
30+
31+
Logical network IP addresses can't connect to management IP pool addresses, due to:
32+
33+
- Incorrect DNS server resolution.
34+
- Firewall rules between the Arc VM logical network and the cloud agent endpoint.
35+
- The logical network is in a different VLAN than the management IP pool and there's no cross-VLAN connectivity.
36+
37+
### Mitigation
38+
39+
To resolve this error, you can take the following steps:
40+
41+
- Make sure that the DNS servers specified in the Arc VM logical network can resolve the MOC cloud agent FQDN.
42+
- Make sure that the logical network IP addresses can connect to all the management IP pool addresses on the required ports. For a detailed list of ports that need to be opened, see [AKS network port and cross-VLAN requirements](aks-hci-network-system-requirements.md#network-port-and-cross-vlan-requirements).
43+
44+
## InternetConnectivityError
45+
46+
Error: Network validation failed during cluster creation.
47+
48+
### Description
49+
50+
Detailed message: `Not able to connect to https://mcr.microsoft.com. Error returned: action failed after 5 attempts: Get "https://mcr.microsoft.com": dial tcp: lookup mcr.microsoft.com on <>: read udp <>: i/o timeout`.
51+
52+
This error indicates that the required URLs are not reachable from the AKS cluster control plane node VM.
53+
54+
### Causes of failure
55+
56+
- Control plane node VM has no outbound internet access.
57+
- Required URLs aren't allowed through the firewall.
58+
59+
### Mitigation
60+
61+
To resolve this error, 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.
62+
63+
## VMNotReachableError
64+
65+
Error: Network validation failed during cluster creation.
66+
67+
### Description
68+
69+
Detailed message: `VM IP : <> is not reachable from management cluster`.
70+
71+
This error indicates that the AKS cluster control plane VM is not reachable from the Arc Resource Bridge (ARB).
72+
73+
### Causes of failure
74+
75+
The Arc VM logical network is not reachable from management IP pool addresses.
76+
77+
### Mitigation
78+
79+
To resolve this error, you can take the following steps:
80+
81+
- Make sure that the management IP pool addresses can reach the logical network IP addresses.
82+
- For a detailed list of ports that need to be opened, see [AKS network port and cross-VLAN requirements](aks-hci-network-system-requirements.md#network-port-and-cross-vlan-requirements).
83+
84+
## DNSResolutionError
85+
86+
This error occurs when DNS servers specified in the Arc VM logical network can't resolve the MOC cloud FQDN or the required URLs.
87+
88+
### Causes of failure
89+
90+
DNS servers specified in a logical network can't resolve the MOC cloud FQDN or the required URLs.
91+
92+
### Mitigation
93+
94+
To resolve this error, check the DNS servers specified in the logical network so that they can resolve the MOC cloud FQDN or the required URLs.
95+
96+
## Contact Microsoft Support
97+
98+
If problems persist, [collect AKS cluster logs](get-on-demand-logs.md) before you [create a support request](aks-troubleshoot.md#open-a-support-request).
99+
100+
## Next steps
101+
102+
[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)

0 commit comments

Comments
 (0)