Skip to content

Commit c2503ff

Browse files
Merge pull request #212700 from JnHs/jh-arcrb-ts926
expand URL info
2 parents 813fe92 + e78a8a3 commit c2503ff

File tree

1 file changed

+26
-25
lines changed

1 file changed

+26
-25
lines changed

articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md

Lines changed: 26 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot Azure Arc resource bridge (preview) issues
33
description: This article tells how to troubleshoot and resolve issues with the Azure Arc resource bridge (preview) when trying to deploy or connect to the service.
4-
ms.date: 08/24/2022
4+
ms.date: 09/26/2022
55
ms.topic: conceptual
66
---
77

@@ -24,7 +24,7 @@ $HOME\.KVA\.ssh\logkey
2424

2525
To run the `az arcappliance logs` command, the path to the kubeconfig must be provided. The kubeconfig is generated after successful completion of the `az arcappliance deploy` command and is placed in the same directory as the CLI command in ./kubeconfig or as specified in `--outfile` (if the parameter was passed).
2626

27-
If `az arcappliance deploy` was not completed, then the kubeconfig file may exist but may be empty or missing data, so it can't be used for logs collection. In this case, the Appliance VM IP address can be used to collect logs instead. The Appliance VM IP is assigned when the `az arcappliance deploy` command is run, after Control Plane Endpoint reconciliation. For example, if the message displayed in the command window reads "Appliance IP is 10.97.176.27", the command to use for logs collection would be:
27+
If `az arcappliance deploy` was not completed, then the kubeconfig file may exist but may be empty or missing data, so it can't be used for logs collection. In this case, the Appliance VM IP address can be used to collect logs instead. The Appliance VM IP is assigned when the `az arcappliance deploy` command is run, after Control Plane Endpoint reconciliation. For example, if the message displayed in the command window reads "Appliance IP is 10.97.176.27", the command to use for logs collection would be:
2828

2929
```azurecli
3030
az arcappliance logs hci --out-dir c:\logs --ip 10.97.176.27
@@ -122,30 +122,31 @@ When the appliance is deployed to a host resource pool, there is no high availab
122122

123123
### Restricted outbound connectivity
124124

125-
If outbound connectivity is restricted by your firewall or proxy server, make sure the URLs listed below are not blocked.
125+
Make sure the URLs listed below are added to your allowlist.
126126

127-
URLS:
127+
#### Proxy URLs used by appliance agents and services
128128

129-
| Agent resource | Description |
130-
|---------|---------|
131-
|`https://mcr.microsoft.com`|Microsoft container registry|
132-
|`https://*.his.arc.azure.com`|Azure Arc Identity service|
133-
|`https://*.dp.kubernetesconfiguration.azure.com`|Azure Arc configuration service|
134-
|`https://*.servicebus.windows.net`|Cluster connect|
135-
|`https://guestnotificationservice.azure.com` |Guest notification service|
136-
|`https://*.dp.prod.appliances.azure.com`|Resource bridge data plane service|
137-
|`https://ecpacr.azurecr.io` |Resource bridge container image download |
138-
|`.blob.core.windows.net`<br> `*.dl.delivery.mp.microsoft.com`<br> `*.do.dsp.mp.microsoft.com` |Resource bridge image download |
139-
|`https://azurearcfork8sdev.azurecr.io` |Azure Arc for Kubernetes container image download |
140-
|`adhs.events.data.microsoft.com ` |Required diagnostic data sent to Microsoft from control plane nodes|
141-
|`v20.events.data.microsoft.com` |Required diagnostic data sent to Microsoft from the Azure Stack HCI or Windows Server host|
129+
|**Service**|**Port**|**URL**|**Direction**|**Notes**|
130+
|--|--|--|--|--|
131+
|Microsoft container registry | 443 | `https://mcr.microsoft.com`| Appliance VM IP and Control Plane IP need outbound connection. | Required to pull container images for installation. |
132+
|Azure Arc Identity service | 443 | `https://*.his.arc.azure.com` | Appliance VM IP and Control Plane IP need outbound connection. | Manages identity and access control for Azure resources |
133+
|Azure Arc configuration service | 443 | `https://*.dp.kubernetesconfiguration.azure.com`| Appliance VM IP and Control Plane IP need outbound connection. | Used for Kubernetes cluster configuration.|
134+
|Cluster connect service | 443 | `https://*.servicebus.windows.net` | Appliance VM IP and Control Plane IP need outbound connection. | Provides cloud-enabled communication to connect on-premises resources with the cloud. |
135+
|Guest Notification service| 443 | `https://guestnotificationservice.azure.com`| Appliance VM IP and Control Plane IP need outbound connection. | Used to connect on-prem resources to Azure.|
136+
|SFS API endpoint | 443 | msk8s.api.cdp.microsoft.com | Host machine, Appliance VM IP and Control Plane IP need outbound connection. | Used when downloading product catalog, product bits, and OS images from SFS. |
137+
|Resource bridge (appliance) Dataplane service| 443 | `https://*.dp.prod.appliances.azure.com`| Appliance VM IP and Control Plane IP need outbound connection. | Communicate with resource provider in Azure.|
138+
|Resource bridge (appliance) container image download| 443 | `*.blob.core.windows.net, https://ecpacr.azurecr.io`| Appliance VM IP and Control Plane IP need outbound connection. | Required to pull container images. |
139+
|Resource bridge (appliance) image download| 80 | `*.dl.delivery.mp.microsoft.com`| Host machine, Appliance VM IP and Control Plane IP need outbound connection. | Download the Arc Resource Bridge OS images. |
140+
|Azure Arc for Kubernetes container image download| 443 | `https://azurearcfork8sdev.azurecr.io`| Appliance VM IP and Control Plane IP need outbound connection. | Required to pull container images. |
141+
|ADHS telemetry service | 443 | adhs.events.data.microsoft.com| Appliance VM IP and Control Plane IP need outbound connection. | Runs inside the appliance/mariner OS. Used periodically to send Microsoft required diagnostic data from control plane nodes. Used when telemetry is coming off Mariner, which would mean any Kubernetes control plane. |
142+
|Microsoft events data service | 443 |v20.events.data.microsoft.com| Appliance VM IP and Control Plane IP need outbound connection. | Used periodically to send Microsoft required diagnostic data from the Azure Stack HCI or Windows Server host. Used when telemetry is coming off Windows like Windows Server or HCI. |
142143

143-
URLs used by other Arc agents:
144+
#### Used by other Arc agents
144145

145-
|Agent resource | Description |
146-
|---------|---------|
147-
|`https://management.azure.com` |Azure Resource Manager|
148-
|`https://login.microsoftonline.com` |Azure Active Directory|
146+
|**Service**|**URL**|
147+
|--|--|
148+
|Azure Resource Manager| `https://management.azure.com`|
149+
|Azure Active Directory| `https://login.microsoftonline.com`|
149150

150151
### Azure Arc resource bridge is unreachable
151152

@@ -350,8 +351,8 @@ When deploying the resource bridge on VMware Vcenter, you may get an error sayin
350351

351352
If you don't see your problem here or you can't resolve your issue, try one of the following channels for support:
352353

353-
* Get answers from Azure experts through [Microsoft Q&A](/answers/topics/azure-arc.html).
354+
- Get answers from Azure experts through [Microsoft Q&A](/answers/topics/azure-arc.html).
354355

355-
* Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience. Azure Support connects the Azure community to answers, support, and experts.
356+
- Connect with [@AzureSupport](https://twitter.com/azuresupport), the official Microsoft Azure account for improving customer experience. Azure Support connects the Azure community to answers, support, and experts.
356357

357-
* [Open an Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md).
358+
- [Open an Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md).

0 commit comments

Comments
 (0)