Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
790 questions
Azure Migration from VMWare - Appliance Configuration Manger Proxy Issue
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 75%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EW%3C/text%3E%3C/svg%3E)
Wurldtech
0
Reputation points
Hello, I'm trying to run a migration from vCenter to Azure using the appliance. In step 2 "Manage credentials and discovery sources" I have created a user with the right permissions, added credentials, and I'm trying to add a discovery source. I've tried via both IP and FQDN, but the appliance can't connect to vCenter. The "Validation Failed" error reads:
The appliance is unable to reach the FQDN/IP address specified for the vCenter Server - '[serverFQDN]:443/sdk' due to the error: Unable to connect to the remote server
After some examination the issue appears to be that reaching "serverFQDN" requires a proxy, but the appliance is going back and adding "serverFQDN" to the Proxy Bypass list in step 1 every time I try and validate the connection in step 2. The migration appliance VM has the proxy set in the windows config, and it can reach "serverFQDN" via the web browser.
Is there any way to stop this behavior and get the Discovery Source to use the configured proxy?
{count} votes
-
SadiqhAhmed-MSFT 44,591 Reputation points Microsoft Employee2024-08-30T20:28:06.91+00:00 @Wurldtech Thank you for reaching out to us!
It sounds like you're encountering a common issue where the Azure Migrate appliance is unable to connect to the vCenter Server due to proxy settings. The appliance is adding the vCenter Server to the Proxy Bypass list, which prevents it from using the configured proxy to reach the server.
Suggest you follow the steps below:
You can manually edit the proxy bypass list to remove the vCenter Server FQDN/IP address. This can be done by accessing the proxy settings on the appliance and ensuring that the vCenter Server is not included in the bypass list.
Ensure that the proxy settings are correctly configured in the Azure Migrate appliance configuration manager. This includes setting the correct proxy address and port, and ensuring that the vCenter Server is not added to the bypass list.
Make sure that the appliance can reach the vCenter Server through the proxy. You can use tools like
telnetorcurlto test the connectivity from the appliance to the vCenter Server via the proxy.Ensure that there are no firewall rules or security settings that might be blocking the connection between the appliance and the vCenter Server. This includes verifying that the necessary ports (e.g., 443) are open and accessible.
Make sure that you created an allowlist for the required URLs and that no proxy or firewall setting is blocking them.
If the update of any appliance component is failing, either rerun the prerequisites or manually update the appliance services.
Source link:
Hope this helps!
Sign in to comment
Sign in to answer