Skip to content

Commit 5b31453

Browse files
committed
Remove a level
1 parent 9e883a2 commit 5b31453

File tree

1 file changed

+16
-18
lines changed

1 file changed

+16
-18
lines changed

AKS-Arc/network-validation-errors.md

Lines changed: 16 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,7 @@ ms.lastreviewed: 05/06/2025
1414

1515
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.
1616

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.
2018

2119
<!-- | Error | Description | Causes of failure | Mitigation recommendations |
2220
|---|---|---|---|
@@ -25,80 +23,80 @@ The following section summarizes the error codes, possible causes of the errors,
2523
| **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. |
2624
| **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. | -->
2725

28-
### CloudAgentConnectivityError
26+
## CloudAgentConnectivityError
2927

3028
Error: Network validation failed during cluster creation.
3129

32-
#### Description
30+
### Description
3331

3432
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`
3533

3634
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.
3735

38-
#### Causes of failure
36+
### Causes of failure
3937

4038
Logical network IP addresses can't connect to management IP pool addresses, due to:
4139

4240
- Incorrect DNS server resolution.
4341
- Firewall rules between the Arc VM logical network and the cloud agent endpoint.<br/>
4442
- The logical network is in a different vlan than the management IP pool and there's no cross-vlan connectivity.
4543

46-
#### Mitigation
44+
### Mitigation
4745

4846
To resolve this error, you can take the following steps:
4947

5048
- Make sure that the DNS servers specified in the Arc VM logical network can resolve the MOC cloud agent FQDN.
5149
- 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.
5250

53-
### InternetConnectivityError
51+
## InternetConnectivityError
5452

5553
Error: Network validation failed during cluster creation.
5654

57-
#### Description
55+
### Description
5856

5957
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`.
6058

6159
This error indicates that the required URLs are not reachable from the AKS cluster control plane node VM.
6260

63-
#### Causes of failure
61+
### Causes of failure
6462

6563
- Control plane node VM has no outbound internet access.
6664
- Required URLs aren't allowed through the firewall.
6765

68-
#### Mitigation
66+
### Mitigation
6967

7068
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.
7169

72-
### VMNotReachableError
70+
## VMNotReachableError
7371

7472
Error: Network validation failed during cluster creation.
7573

76-
#### Description
74+
### Description
7775

7876
Detailed message: `VM IP : <> is not reachable from management cluster`.
7977

8078
This error indicates that the AKS cluster control plane VM is not reachable from the Arc Resource Bridge (ARB).
8179

82-
#### Causes of failure
80+
### Causes of failure
8381

8482
The Arc VM logical network is not reachable from management IP pool addresses.
8583

86-
#### Mitigation
84+
### Mitigation
8785

8886
To resolve this error, you can take the following steps:
8987

9088
- Make sure that the management IP pool addresses can reach the logical network IP addresses.
9189
- 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.
9290

93-
### DNSResolutionError
91+
## DNSResolutionError
9492

9593
This error occurs when DNS servers specified in the Arc VM logical network can't resolve the MOC cloud FQDN or the required URLs.
9694

97-
#### Causes of failure
95+
### Causes of failure
9896

9997
DNS servers specified in logical network can't resolve the MOC cloud FQDN or the required URLs.
10098

101-
#### Mitigation
99+
### Mitigation
102100

103101
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.
104102

0 commit comments

Comments
 (0)