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/network-validation-errors.md
+16-18Lines changed: 16 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,7 @@ ms.lastreviewed: 05/06/2025
14
14
15
15
This article provides guidance on identifying and resolving various network validation errors encountered during cluster creation, emphasizing 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
16
17
-
## General network validation errors
18
-
19
-
The following section summarizes the error codes, possible causes of the errors, and mitigation steps.
17
+
The article summarizes the error codes, possible causes of the errors, and mitigation steps.
@@ -25,80 +23,80 @@ The following section summarizes the error codes, possible causes of the errors,
25
23
| **VMNotReachableError** <br/> Error: Network validation failed during cluster creation. Detailed message: `VM IP : <> is not reachable from management cluster` | This error indicates that the AKS cluster control plane VM is not reachable from the Arc Resource Bridge (ARB). | The Arc VM logical network is not reachable from management IP pool addresses. | - Make sure that the management IP pool addresses can reach the logical network IP addresses. <br/> - 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. |
26
24
| **DNSResolutionError** | This error occurs when DNS servers specified in the Arc VM logical network can't resolve the MOC cloud FQDN or the required URLs. | DNS servers specified in logical network can't resolve the MOC cloud FQDN or the required URLs. | Check the DNS servers specified in the logical network so that they can resolve the MOC cloud FQDN or the required URLs. | -->
27
25
28
-
###CloudAgentConnectivityError
26
+
## CloudAgentConnectivityError
29
27
30
28
Error: Network validation failed during cluster creation.
31
29
32
-
####Description
30
+
### Description
33
31
34
32
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`
35
33
36
34
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.
37
35
38
-
####Causes of failure
36
+
### Causes of failure
39
37
40
38
Logical network IP addresses can't connect to management IP pool addresses, due to:
41
39
42
40
- Incorrect DNS server resolution.
43
41
- Firewall rules between the Arc VM logical network and the cloud agent endpoint.<br/>
44
42
- The logical network is in a different vlan than the management IP pool and there's no cross-vlan connectivity.
45
43
46
-
####Mitigation
44
+
### Mitigation
47
45
48
46
To resolve this error, you can take the following steps:
49
47
50
48
- Make sure that the DNS servers specified in the Arc VM logical network can resolve the MOC cloud agent FQDN.
51
49
- 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.
52
50
53
-
###InternetConnectivityError
51
+
## InternetConnectivityError
54
52
55
53
Error: Network validation failed during cluster creation.
56
54
57
-
####Description
55
+
### Description
58
56
59
57
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`.
60
58
61
59
This error indicates that the required URLs are not reachable from the AKS cluster control plane node VM.
62
60
63
-
####Causes of failure
61
+
### Causes of failure
64
62
65
63
- Control plane node VM has no outbound internet access.
66
64
- Required URLs aren't allowed through the firewall.
67
65
68
-
####Mitigation
66
+
### Mitigation
69
67
70
68
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.
71
69
72
-
###VMNotReachableError
70
+
## VMNotReachableError
73
71
74
72
Error: Network validation failed during cluster creation.
75
73
76
-
####Description
74
+
### Description
77
75
78
76
Detailed message: `VM IP : <> is not reachable from management cluster`.
79
77
80
78
This error indicates that the AKS cluster control plane VM is not reachable from the Arc Resource Bridge (ARB).
81
79
82
-
####Causes of failure
80
+
### Causes of failure
83
81
84
82
The Arc VM logical network is not reachable from management IP pool addresses.
85
83
86
-
####Mitigation
84
+
### Mitigation
87
85
88
86
To resolve this error, you can take the following steps:
89
87
90
88
- Make sure that the management IP pool addresses can reach the logical network IP addresses.
91
89
- 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.
92
90
93
-
###DNSResolutionError
91
+
## DNSResolutionError
94
92
95
93
This error occurs when DNS servers specified in the Arc VM logical network can't resolve the MOC cloud FQDN or the required URLs.
96
94
97
-
####Causes of failure
95
+
### Causes of failure
98
96
99
97
DNS servers specified in logical network can't resolve the MOC cloud FQDN or the required URLs.
100
98
101
-
####Mitigation
99
+
### Mitigation
102
100
103
101
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.
0 commit comments