Tweaks

Author: sethmanheim

AKS-Arc/network-validation-errors.md

@@ -18,17 +18,17 @@ This article provides guidance on identifying and resolving various network vali
 
 The following table summarizes the error codes, possible causes of the errors, and mitigation steps.
 
-|     Error  |    Description  |    Causes of failure  |    Mitigation recommendation  |
+|     Error  |    Description  |    Causes of failure  |    Mitigation recommendations  |
 |---|---|---|---|
 |    **CloudAgentConnectivityError** <br/> Error: Network validation failed during cluster creation. 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`  | 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 DNS servers specified in AKS Arc logical network are unable to resolve the MOC cloud agent FQDN.  | 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 DNS servers specified in the AKS Arc logical network can resolve the MOC cloud agent FQDN.<br/>  - 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.    |
 |    **InternetConnectivityError** <br/> Error: Network validation failed during cluster creation. 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`   | This error indicates that the required URLs are not 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.  |
 |    **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 AKS Arc 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.    |
-|    **DNSResolutionError**      | This error occurs when DNS servers specified in the AKS Arc 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.  |
+|    **DNSResolutionError**      | This error occurs when DNS servers specified in the AKS Arc 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.  |
 
 ## Contact Microsoft Support
 
 If the problem persists, [collect AKS cluster logs](get-on-demand-logs.md) before you [create the support request](aks-troubleshoot.md#open-a-support-request).
 
 ## Next steps
 
-- [Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)
+[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)