Skip to main content

Network requirements

LiveData Migrator deploys an agent to your Hadoop edge node to migrate data from your on-premises network to Azure. To use LiveData Migrator, you need to make outbound connections from your network to several Azure endpoints, including regional endpoints.

note

Because LiveData Migrator uses Azure service buses to communicate with Microsoft Azure, you don't need to make any inbound connections.

LiveData Migrator endpoint requirements​

Configure your firewall to make sure your on-premises network can reach the following endpoints for your chosen region.

See the Prerequisites page for a list of all supported regions.

EndpointPortUsed forService tag range/IP address range
pkg.wandisco.com443Downloading and running the installer3.249.118.106
wdfrpdeployments.blob.core.windows.net443Downloading and running the installerStorage.WestCentralUS & AzureCloud.westcentralus
wdfrpdeployments.afd.azureedge.net / cdn.wandisco.com443Downloading and running the installerAzureFrontDoor.Frontend
[account_name].dfs.core.windows.net *443Data migration with HTTPSStorage.WestCentralUS
wd-frp-prod-sb-1.servicebus.windows.net5671AMQP messagingEventHub.WestUS
ldm-metrics-prod.servicebus.windows.net5671AMQP messagingEventHub.WestUS
dc.applicationinsights.azure.com443Azure MetricsAzureMonitor.WestCentralUS
dc.applicationinsights.microsoft.com443Azure MetricsAzureMonitor.WestCentralUS
dc.services.visualstudio.com443Azure MetricsAzureMonitor.WestCentralUS
westus2-0.in.applicationinsights.azure.com443Azure MetricsAzureMonitor.WestUS2
[servername].database.windows.net *1433Optional SQL server for Hive metadataSql.WestCentralUS
login.microsoftonline.com443Active DirectoryAzureActiveDirectory.ServiceEndpoint & AzureCloud.westcentralus

*[Servername] represents your Azure SQL server's name and [account_name] represents your Azure account name. The endpoints for these assume your server and account are situated in the selected region.

If you're using a DNS firewall, you only need to whitelist each endpoint name to allow your network access. If this doesn't work, configure the on-premises firewall to allow access to the full IP ranges used for each service:

  1. Access Microsoft's published service tag IP ranges. These IP ranges are owned by Microsoft and route to trusted Azure Services.
  2. Look up the service tags for each endpoint from the table above.
  3. Locate the regional service tag that ends in your region name. For example, WestCentralUS or JapanWest.
  4. Whitelist outbound connections to each of the IPs listed in the range.

You don't have to whitelist the entire global range, such as AzureCloud. But if you do, your network will be able to access all of the necessary endpoints.

note

Microsoft regularly updates the IP ranges of their services, adding or removing IPs. If you've only whitelisted the IPs and you encounter problems connecting to endpoints later, you may need to download a new copy of the IP range list and update your firewall rules to whitelist the relevant new IP addresses.

Test connection to LiveData Migrator endpoints​

LiveData Migrator automatically tests your network's connection to all of the necessary endpoints when you install it. After you install LiveData Migrator, you can run this script file to test endpoint connections again:

/opt/wandisco/environment-checks/env-checks.sh

If the Hadoop edge node can't connect to any of the endpoints, LiveData Migrator won't function correctly. Make sure you can connect to each endpoint before you use LiveData Migrator.

Create a support ticket if you need help setting up your network.

Next steps​

You're ready to install LiveData Migrator for Azure.