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: articles/storage-mover/network-prerequisites.md
+15-13Lines changed: 15 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,37 +46,39 @@ A storage mover agent supports both SMB and NFS clients. The following list of p
46
46
47
47
The following table provides a summary of the required services, their endpoint types, and whether private access is supported. Because your network settings must allow the Storage Mover Agent to connect over HTTPS to the service's endpoints, the Fully Qualified Domain Name (FQDN) is also included.
48
48
49
-
# [Public Cloud](#tab/public)
49
+
<!--# [Public Cloud](#tab/public)-->
50
50
51
51
| Service | Needed For | Supports Private Endpoints | FQDN |
The following sections detail the required components, public endpoint dependencies, and networking considerations for deploying Storage Mover in a private network.
82
84
@@ -104,7 +106,7 @@ The following diagram illustrates an example of a resource topology for enabling
104
106
> [!NOTE]
105
107
> This configuration is one of many possible setups for a private network and doesn't encompass all components involved in network configuration, such as DNS, proxies, and virtual network peering.
106
108
107
-
:::image type="content" source="media/network-prerequisites/networking-topology.png" alt-text="A diagram illustrating an example of a resource topology for enabling private connectivity to all endpoints that support it.":::
109
+
:::image border="false" type="content" source="media/network-prerequisites/networking-topology-sml.png" alt-text="A diagram illustrating an example of a resource topology for enabling private connectivity to all endpoints that support it." lightbox="media/network-prerequisites/networking-topology-lrg.png":::
108
110
109
111
<sup>1</sup> Arc Private Link Scopes provide access to three Arc services as shown in the image. The *Extensions* Arc service isn't used by the Storage Mover Agent. It appears muted in the image to avoid confusion.<br>
110
112
<sup>2</sup> Arc Private Link Scopes and the three Arc services to which they connect can both be accessed directly over public endpoints. The Arc Private Link Scope can be configured to enable or disable public network access.<br>
@@ -116,10 +118,10 @@ Despite the emphasis on private networking, certain required Storage Mover servi
116
118
117
119
The following endpoints *must* be accessible over public endpoints for the Storage Mover Agent to function correctly:
118
120
119
-
-**MCR** for automated agent updates.
121
+
-**Microsoft Artifact Registry** for automated agent updates.
120
122
-**The Storage Mover Service** for agent heartbeats and job coordination.
121
-
-**Event Hub** for publishing copy logs.
122
-
-**AAD/Entra ID** for registration and identity management.
123
+
-**Event Hubs** for publishing copy logs.
124
+
-**Azure AD/Microsoft Entra ID** for registration and identity management.
123
125
-**Azure Resource Manager** for registration and resource management.
124
126
125
127
## Arc-enabled server considerations
@@ -135,11 +137,11 @@ A Private Link Scope allows you to maintain private connectivity by facilitating
135
137
136
138
Beyond the core components, there are networking considerations that can be configured to enhance the security and functionality of the Storage Mover Agent. However, these configurations are optional, depend on your specific network requirements, and might affect networking performance - especially if misconfigured.
137
139
138
-
### Proxy Support
140
+
### Proxy support
139
141
140
142
The Storage Mover Agent supports external HTTP and HTTPS proxies. Configuration is done via the agent's shell within the **Network Configuration** section's **Update network configuration** menu. When prompted, select **Proxy** and enter the Fully Qualified Domain Name (FQDN) or IP address of the proxy. Include the port number if necessary. The following example illustrates the configuration steps:
141
143
142
-
:::image type="content" source="media/network-prerequisites/proxy-configuration.png" alt-text="A screenshot showing the proxy configuration screen in the Storage Mover Agent.":::
144
+
:::image type="content" source="media/network-prerequisites/proxy-configuration-sml.png" alt-text="A screenshot showing the proxy configuration screen in the Storage Mover Agent." lightbox="media/network-prerequisites/proxy-configuration-lrg.png":::
143
145
144
-
### SSL Inspection
146
+
### SSL inspection
145
147
If your network performs SSL interception, the agent might fail to recognize modified certificates. Currently, adding custom certificates to the agent isn't supported. To avoid issues, add required endpoints to the allowlist to bypass SSL inspection. These endpoints are available in the [Networking overview](#networking-overview) section.
Copy file name to clipboardExpand all lines: articles/storage-mover/network-troubleshooting.md
+86-3Lines changed: 86 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,9 @@ ms.date: 10/22/2025
9
9
ms.custom: template-how-to
10
10
---
11
11
12
-
# Troubleshooting network issues with the Azure Storage Mover Agent
12
+
# Troubleshooting network issues with the Azure Storage Mover agent
13
13
14
-
The Azure Storage Mover Agent is an important part of the Azure Storage Mover service, a powerful tool for seamlessly migrating data to Azure. The agent's functionality depends heavily on reliable network connectivity. When network issues arise, The Azure Storage Mover Agent provides a robust set of tools for diagnosing and resolving network issues.
14
+
The Azure Storage Mover agent is an important part of the Azure Storage Mover service, a powerful tool for seamlessly migrating data to Azure. The agent's functionality depends heavily on reliable network connectivity. When network issues arise, the Azure Storage Mover agent provides a robust set of tools for diagnosing and resolving network issues.
15
15
16
16
By following a structured approach, starting with configuration checks, progressing through connectivity tests, and applying endpoint diagnostics, administrators can ensure reliable operation and successful data migrations. For persistent or complex issues, the support bundle offers a path to deeper analysis and assistance from Microsoft Support.
17
17
@@ -75,7 +75,7 @@ For general connectivity testing, select the **Test Network Connectivity** optio
75
75
- Proxy usage
76
76
77
77
> [!NOTE]
78
-
> Note: This test doesn't include Storage Account or Key Vault endpoints used during job execution.
78
+
> This test doesn't include Storage Account or Key Vault endpoints used during job execution.
79
79
80
80
### Verbose network checks
81
81
@@ -89,6 +89,89 @@ The `Test single endpoint connectivity` option allows you to test the connectivi
89
89
-`traceroute` for path analysis
90
90
-`curl` for HTTPS connectivity
91
91
92
+
The following example provides sample output from the tool:
93
+
94
+
```Output
95
+
1) Show network configuration
96
+
2) Update network configuration
97
+
3) Test network connectivity
98
+
4) Test network connectivity verbosely
99
+
5) Test single endpoint connectivity
100
+
6) Quit
101
+
102
+
Choice: 5
103
+
This option tests connectivity to one endpoint with your current network setup using tools like nslookup, traceroute, curl, etc.
104
+
Provide an Azure endpoint (URL or FQDN) to test: https://mydemoaccount.blob.core.windows.net/demo-nfs4-file-share
Testing 'mydemoaccount.blob.core.windows.net' port 443 over TCP...
123
+
124
+
traceroute to mydemoaccount.blob.core.windows.net (10.60.14.164), 30 hops max, 60 byte packets
125
+
1 cgbslon66ca901-Te0-0-0-16-2620.network.microsoft.com (10.126.12.2) 0.401 ms 0.440 ms 0.507 ms
126
+
2 musmtvsvcanrl1-Eth23-1.network.microsoft.com (10.10.80.2) 0.279 ms musmtvsvcanrl2-Eth23-1.network.microsoft.com (10.10.80.6) 0.267 ms musmtvsvcanrl1-Eth23-1.network.microsoft.com (10.10.80.2) 0.305 ms
127
+
3 musmtvsvcanrb1-Eth25-1.network.microsoft.com (10.126.137.144) 0.303 ms musmtvsvcanrb3-Eth33-1.network.microsoft.com (10.126.137.156) 0.230 ms musmtvsvcanrb2-Eth25-1.network.microsoft.com (10.126.137.146) 0.279 ms
128
+
4 musmtv005anrs2-ethernet31-1.clouddatahub.net (10.126.137.139) 0.274 ms 0.262 ms musmtvsvcanrs2-Eth30-1.network.microsoft.com (10.126.137.141) 0.250 ms
129
+
5 10.161.128.7 (10.161.128.7) 0.123 ms 10.161.128.21 (10.161.128.21) 0.216 ms 10.161.128.7 (10.161.128.7) 0.218 ms
130
+
6 musmtvsvcanrs1-Eth15-1-22.network.microsoft.com (10.161.128.4) 0.323 ms 0.337 ms 0.273 ms
131
+
7 musmtvsvcanrb3-Eth29-1.network.microsoft.com (10.126.137.4) 0.329 ms musmtvsvcanrb4-Eth29-1.network.microsoft.com (10.126.137.6) 0.553 ms musmtvsvcanrb2-Eth29-1.network.microsoft.com (10.126.137.2) 0.306 ms
132
+
8 musmtvsvcanrc2-Eth5-1.network.microsoft.com (10.126.137.9) 0.393 ms 0.326 ms musmtvsvcanrc1-Eth5-1.network.microsoft.com (10.126.137.1) 0.382 ms
133
+
9 cusmtvsvcca901-Bu12.network.microsoft.com (10.37.12.118) 0.800 ms 10.37.12.120 (10.37.12.120) 0.870 ms 0.814 ms
134
+
10 * * *
135
+
11 * * *
136
+
12 * * *
137
+
13 cussclb21ca940-Hu0-0-0-0.network.microsoft.com (10.37.12.104) 2.850 ms cussclb21ca940-Hu0-0-0-1.network.microsoft.com (10.37.12.106) 2.126 ms cussclb21ca940-Hu0-0-0-0.network.microsoft.com (10.37.12.104) 2.560 ms
138
+
14 cussclb21an7k1-Po92-11.network.microsoft.com (10.37.171.33) 0.787 ms 0.826 ms 0.814 ms
139
+
15 10.37.171.70 (10.37.171.70) 1.077 ms 1.056 ms 1.040 ms
140
+
16 dussclb21an7k1-Po21-11.network.microsoft.com (10.37.168.4) 1.221 ms 1.295 ms 1.212 ms
141
+
17 dussclb21a7201-Po7.network.microsoft.com (169.220.17.1) 1.168 ms 1.351 ms 1.340 ms
142
+
18 ae60-0.car01.region.ntwk.msn.net (203.44.15.46) 2.153 ms 1.319 ms 1.306 ms
143
+
19 ae22-0.icr01.region.ntwk.msn.net (203.44.232.202) 1.382 ms ae24-0.icr02.region.ntwk.msn.net (203.44.232.204) 1.370 ms 1.717 ms
144
+
20 be-120-0.ibr03.region.ntwk.msn.net (203.44.22.167) 17.054 ms * *
145
+
21 be-2-0.ibr04.region.ntwk.msn.net (203.44.17.23) 16.926 ms * be-2-0.ibr03.region.ntwk.msn.net (203.44.17.21) 17.911 ms
146
+
22 * be-5-0.ibr02.region.ntwk.msn.net (203.44.17.71) 116.530 ms 116.798 ms
147
+
23 169.10.19.29 (169.10.19.29) 18.540 ms 18.096 ms *
148
+
24 * 169.10.6.142 (169.10.6.142) 18.161 ms 169.10.11.182 (169.10.11.182) 18.559 ms
149
+
25 169.10.11.174 (169.10.11.174) 17.550 ms 169.10.11.170 (169.10.11.170) 17.132 ms *
150
+
26 * * *
151
+
27 * * 192.98.222.143 (192.98.222.143) 15.860 ms
152
+
28 * 127.106.199.121 (127.106.199.121) 16.719 ms 127.106.199.111 (127.106.199.111) 16.341 ms
153
+
29 127.106.199.112 (127.106.199.112) 16.521 ms * 127.106.199.109 (127.106.199.109) 16.200 ms
Within the `Service and job Status` menu, two tools are available for assessing the health of the agent's connection to the Storage Mover Service and the status of job executions. These tools, the **Service Communication Status** and **Job Summary, Details, and Copy logs**, help assess the Agent's registration status and job execution health.
0 commit comments