Hyper-V could not replicate, status critical , error 0x00002EFE

Question

I use Hyper-v replication on Windows server 2016. I have many guest , If guest OS is Linux like Ubuntu Server it's OK but if guest OS is Windows Server replication is error . First time I enable Replication to DR-site it's OK all guest but in a few hours only guest OS is windows is error and show status critical.

I try to remove replication and enable replication again but result is same. I view a error detail it's show log below
"Hyper-V could not replicate changes for virtual machine 'myname': The connection with the server was terminated abnormally (0x00002EFE). " How to resolve this problem. Thank you.

Answer 1

Hi Numchoke Kunmunwong,

I would like to Suggest to check replication requirement(Ports, Authentication) status. Please visit the link below.
https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/set-up-hyper-v-replica This error mainly occurs due the the following listed reasons, please kindly check this too.

1. Firewall open on the replica server with the right ports, build in rules for Hyper-V replication port enabled.
2. The Hyper-V version on the replica is the same or newer & supported then the incoming Hyper-V server.
3. If it is certificate base authentication, make sure all the servers involve included as subjects in the certificate the short NAME+FQDN name including the name of the Hyper-V broker (if you are replicating from cluster), also make sure that you have set the right certificate on the replica server.

Best Regards,

Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

While the above might be true in some cases, the solution is to make sure that one users actual name of the machine (and not some secondary SAN name in certificate - something that might have been recommended in various blogs - it might have worked years ago this way)

That is because WinRM in involved in the replication & you get

If you want to send the traffic via another VLAN (like Live Migration and not the main management vlan), make sure that using hosts file on the source HV server, the ACTUAL name of the replica machine resolves to the VLAN-you-want-to-use IP

So if the hostname is ie RealHV-Host.domain.local with IP 10.10.10.1 but SAN also has vhost01.domain.local & using host file one can resolves that to 172.15.0.1

you will get an error:

Enable-VMReplication : The operation on computer 'vhost01.domain.local' failed: WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer vhost01.domain.local. Verify that the computer exists on the network and that the name provided is spelled correctly.

Just "cheat" using host file & make sure RealHV-Host.domain.local resolves to 172.15.0.1