Azure Migrate Unable to start replication as on-premise appliance is not discovered even though it is connected and the cluster has been added.

Cristopher Klint 25

Hi,

I am migrating from 2016 S2D cluster to ASHCI cluster and have created the source appliance, I have discovered the VMs in the source cluster so they are visible in Azure. When I go into the replicate wizard in Azure and try to choose the On-Premises Appliance the list is empty and I get this error "Couldn't find connected appliances. Deploy an appliance by completing the Discover step of migration for your on-premises environment."

Cluster name omitted in picture below User's image

Appliance connection status (all services seem to be connected

User's image

Why is my appliance not showing up?

Cristopher Klint 25 Reputation points

2024-10-21T09:05:20.46+00:00

and to add my VMs in the source cluster have been discovered
Rahul Podila 430 Reputation points Microsoft Vendor

2024-10-22T07:31:44.6833333+00:00

Hi @Cristopher Klint
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

The device is properly connected to Azure, which can be verified in device configuration. Additionally, check your firewall settings to make sure they are not blocking connections; The ports required for Azure migration must be open. It can also be helpful to go through the reconfiguration process to make sure everything is documented correctly.

Please confirm that your device and Azure resources are in the same location, as having them in different regions can cause issues. Make sure your Azure account has the correct permissions to access the tool. Sometimes temporary problems can be fixed by simply closing and reopening the replication wizard. If the problem persists, consider restarting services on the machine and reviewing the logs to give us more insight.
if any doubts please go through this link :- https://learn.microsoft.com/en-us/azure/migrate/migrate-appliance

If you have any further queries, do let us know

--------------------------------------------------------------------------------------------------------

If the answer is helpful, please click "Accept Answer" and "Upvote it".
Rahul Podila 430 Reputation points Microsoft Vendor

2024-10-23T05:21:45.7733333+00:00

Hi @Cristopher Klint
If you had a chance to see my comment to your question. If it was helpful, please click "Upvote" on my post let us know Thank you...!
Cristopher Klint 25 Reputation points

2024-10-23T06:43:16.22+00:00

Hi,

Many thanks for your response. We have verified no traffic is blocked in the firewall. I have setup a new appliance already but with the same result. Running diagnostics on the appliance does not indicate any issue either. Thank you for the link, it states that the appliance should run on a Hyper-V host on at least Server 2019 but my source cluster is 2016

https://learn.microsoft.com/en-us/azure/migrate/migrate-appliance

In this link in the topology it looks like the source appliance should run in the source cluster so that is what I setup

https://learn.microsoft.com/en-us/azure-stack/hci/migrate/migration-azure-migrate-hci-overview

And according to this link migrating from Server 2016 should be perfectly supported and here it doesn't say anything about Hyper-V Server OS version hosting the appliance.

https://learn.microsoft.com/en-us/azure-stack/hci/migrate/migrate-hyperv-requirements

1 answer

Rahul Podila 430 Reputation points Microsoft Vendor

2024-10-25T02:20:26.87+00:00

Hi @Cristopher Klint
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
I can help you with that! Based on the information you provided, it seems like the issue might be related to the version of the Hyper-V host that is running the appliance. The documentation states that the appliance should run on a Hyper-V host on at least Server 2019, but you mentioned that the source cluster is running on Windows Server 2016.

To resolve this issue, you can try the following steps:

Check if the Hyper-V host that is running the appliance meets the minimum requirements. According to the documentation, the appliance should run on a Hyper-V host on at least Server 2019.

If the Hyper-V host is running on an older version of Windows Server, try upgrading it to Server 2019 or a later version.

If upgrading the Hyper-V host is not possible, you can try running the appliance on a different Hyper-V host that meets the minimum requirements.

If the issue persists, you can try contacting Microsoft support for further assistance. They might be able to provide more detailed logs or help you troubleshoot the issue further.
If you have any further queries, do let us know

If the answer is helpful, please click "Accept Answer" and "Upvote it"
Please sign in to rate this answer.
Rahul Podila 430 Reputation points Microsoft Vendor

2024-10-28T01:12:38.4966667+00:00

Hi @Cristopher Klint If you had a chance to see my comment to your question. If it was helpful, please click "Upvote" on my post let us know Thank you...!

Cristopher Klint 25 Reputation points

2024-10-28T08:05:29.5533333+00:00

Hi, I can't say that it has helped me move forward I will try and open a support case for this, but thank you for your efforts

Rahul Podila 430 Reputation points Microsoft Vendor

2024-10-29T06:53:17.58+00:00

Hi @Cristopher Klint
"I'm sorry to hear that my suggestions did not help you move forward with your issue. If you are still experiencing the same issue, I would recommend opening a support case with Microsoft. They will be able to provide more detailed logs and help you troubleshoot the issue further.
If you have any further queries, do let us know

If the answer is helpful, please click "Accept Answer" and "Upvote it"
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Migrate Unable to start replication as on-premise appliance is not discovered even though it is connected and the cluster has been added.

1 answer

Your answer