Hi
We are having a problem enabling replication on our VMs.
we have two hyper visors each running 2012r2.
The Hyper-V manager is being run from win8.1

They are not clustered. The ports have been opened in the firewall (and for testing I have turned off the firewall).  both servers are using HTTP  kerberos and have been delegated in the AD.

If i set up a vm on hyper-A then try to enable replication to hyper-B i get the following error:
hyper-v failed to enable replication for virtual machine. The server name or address could not be resolved (0x00002EE7)
If I set up a vm on hyper-B and try to enable replication to hyper-A it works fine.
I can ping both servers from each other
I have tied the "fix" suggested here

Does any one else have a suggestion to try?

Rob

Hi Rob,

I have read the "fix" you posted.

My concern about " I have tied the 'fix' suggested here "   is  "Under Local Computer Policy" , because your servers are in  the domain , i mean that did you "fix" replica server under  " Domain Policy " ?

Best Regards

Elton Ji

Hi Elton

I adjusted the name resolution policy under the Local Computer Policy on both servers.

Thanks for looking at this.

Rob

Hi Rob,

I mean that you need to do the " fix " under "Domain Policy" , because the "Domain Policy" will take precedence over "Local Policy " .

Any further information , please feel free to let us know .

Best Regards

Elton Ji

Hi Elton

I have adjusted the name resolution policy via a group policy through "group policy management" as well.

Have I missed something here?

Thanks

Rob

Hi ,

Sorry for the misunderstanding.

After rebooting the servers , the replica issue persists ?

Best Regards

Elton Ji

I will restart the servers later tonight and let you know how it goes.

thanks again

Rob

Ok 

I restarted both servers last night and this morning there is no change regarding this problem.

Rob

Hi Rob ,

Did you check the "Hyper-B" entry in the forward zone and the reverse zone your DNS server ?

Best Regards

Elton Ji

I have checked the DNS records:

forward records are set up the same for both hyper visors (obviously the IP and name are different) in the reverse zone they are set up the same however hyper-b has a time stamp and hyper-a is static.

I have run ipconfig on both hosts and they also return the same values.

Thanks

Rob

Hi,

So strange , did you try to rejoin hyper-b to the domain  ?

Best Regards

Elton Ji

Hi Rob,

Has the problem been solved ?

Best Regards

Elton Ji

Hi Langdon

Can you provide the exact server name (is it hyper-B) and the FQDN? Can you also check if the network listener required for Hyper-V Replica is running on Hyper-B - send us the output of 'netsh http show servicestate' from Hyper-B and ensure that the port and server which you are providing as part of enabling replication of a VM from Hyper-A is consistent with the netsh output.

Thanks

Praveen

Hi Elton and Praveen,

Thanks for sticking with me.

I am working in a school and the buildings have been shut down over the holiday period so i am unable to do very much from home.  

Will take a fresh look at this on monday and send the output requested.

Thanks

rob

Hi

The port we are using is 1337.

here is the netsh output:

Snapshot of HTTP service state (Server Session View):
-----------------------------------------------------

Server session ID: FF00000220000001
    Version: 1.0
    State: Active
    Properties:
        Max bandwidth: 4294967295
        Timeouts:
            Entity body timeout (secs): 120
            Drain entity body timeout (secs): 120
            Request queue timeout (secs): 120
            Idle connection timeout (secs): 120
            Header wait timeout (secs): 120
            Minimum send rate (bytes/sec): 150
    URL groups:
    URL group ID: FE00000240000001
        State: Active
        Request queue name: Request queue is unnamed.
        Properties:
            Max bandwidth: inherited
            Max connections: inherited
            Timeouts:
                Timeout values inherited
            Number of registered URLs: 2
            Registered URLs:
                HTTP://+:5985/WSMAN/
                HTTP://+:47001/WSMAN/

Server session ID: FF00000020000001
    Version: 2.0
    State: Active
    Properties:
        Max bandwidth: 4294967295
        Timeouts:
            Entity body timeout (secs): 120
            Drain entity body timeout (secs): 120
            Request queue timeout (secs): 120
            Idle connection timeout (secs): 120
            Header wait timeout (secs): 120
            Minimum send rate (bytes/sec): 150
    URL groups:
    URL group ID: FE00000040000001
        State: Active
        Request queue name: Request queue is unnamed.
        Properties:
            Max bandwidth: inherited
            Max connections: inherited
            Timeouts:
                Entity body timeout (secs): 300
                Drain entity body timeout (secs): 0
                Request queue timeout (secs): 0
                Idle connection timeout (secs): 300
                Header wait timeout (secs): 0
                Minimum send rate (bytes/sec): 0
            Number of registered URLs: 2
            Registered URLs:
                HTTP://HYPER-B:1337/HVRROOT_{FED10A98-8CB9-41E2-8608-264B923C2623}/
                HTTP://HYPER-B.UPHOLLAND.LANCSNGFL.AC.UK:1337/HVRROOT_{FED10A98-8CB9-41E2-8608-264B923C2623}/

Request queues:
    Request queue name: Request queue is unnamed.
        Version: 1.0
        State: Active
        Request queue 503 verbosity level: Basic
        Max requests: 1000
        Number of active processes attached: 1
        Process IDs:
            896

    Request queue name: Request queue is unnamed.
        Version: 2.0
        State: Active
        Request queue 503 verbosity level: Basic
        Max requests: 1000
        Number of active processes attached: 1
        Process IDs:
            352


[Hyper-B.upholland.lancsngfl.ac.uk]: PS C:\Users\Robert\Documents>

Thanks

Rob

Hi

Been following up some ideas last week.

decided to look into the hardware since this appears to be the only difference between the systems.

Hyper-B is an HP Proliant server.  the onboard NIC had a driver update available however it was only available for 2012 not R2.  So I wiped the OS and installed 2012 updated the intel drivers and then teamed the NIC.  When i then tried to replicate I got an error because the OS was different.  I then ran an in place upgrade to 2012r2 which carried the drivers over to the new OS.  I had to re-team the NIC and then when I tried to replicate it worked fine!  I then decided to do a reboot of the system, however after this I appear to be back to square one again with the same error message that started the whole thing off.

Any thoughts would be greatly appreciated.

Thanks

Rob

Hi Rob

Are you facing the problem during replication or during planned failover (when reverse replication kicks in)? Can you confirm if the following are in order:

1) Name resolution for the replica server happens as expected (for HYPER-B or HYPER-B.UPHOLLAND.LANCSNGFL.AC.UK)

2) Are you providing the short name or the FQDN as part of enabling replication (eg: HYPER-B or HYPER-B.UPHOLLAND.LANCSNGFL.AC.UK)

3) The network listeners on the replica server are available on the same name as the one which is being provided in enable replication (eg: HYPER-B or HYPER-B.UPHOLLAND.LANCSNGFL.AC.UK)

4) If you are using Windows Firewall, Hyper-V Replica corresponding firewall rules are enabled?

5) Is replication happening in one direction (from B->A)?

Praveen

Hi Praveen

The error occurs when I try and set up replication from A to B

It also occurs during a planned fail over at the reverse replication stage from A to B.

1. the name resolution happens as expected for the replica server (hyper-B).

2. the FQDN is used as part of enabling replication.

3.Please can you give me a little more help with checking this one.

4. the fire wall is turned off for this.

5.  yes replication is happening from B to A.

For (3) - it's the same step as before - run the "netsh http show servicestate | findstr -i hvrroot" on B and check if you can see two listeners. Ensure that the name and port which you provide in A is same as what is seen in the output of the above command (eg: HYPER-B.UPHOLLAND.LANCSNGFL.AC.UK on port 1337)

It's interesting to note that B to A is working. What is the network connectivity between the two sites, is there any proxy server in the setup? What is the authentication scheme which is being used (Kerberos?) - is it the same when you are able to successfully replicate from B->A.

Praveen

... and, can you also copy-paste the error which is seen on the screen?

Praveen

Hi Praveen

the network listeners on both servers are OK.

The network set up is:  the two servers are currently sitting next to each other (whilst we set it up) and they both connect to the same switch.

The authentication used kerberos.

Rob

Hi

here is the error message I get with both initial replication and reverse replication:

Hyper-V failed to enable reverse replication.

Hyper-V failed to resolve the Replica server name.

hyper-V failed to enable reverse replication for "TestVM": The servername or address could not be resolved (0x002EE7). (Virtual machine ID 1D5ECFA4-EC4E-43FD-90DC-AD063CCACD75)

Hyper-V failed to resolve the replica server "Hyper-B.upholland.lancsngfl.ac.uk" name. Verify that the Replica server name provided is correct.

Rob

That's strange.

Can you try changing the replica (Hyper-B.upholland.lancsngfl.ac.uk) listener's port number from 1337 to say 80? You can do this in the UI in 'Enabled this server as a replica server' where you specify Kerberos and this port. Once you make the change, re-running the netsh command should show that the listeners are capable of receiving the replication traffic in port 80. Now enable replication from A->B and give the new port number (80).

Can you also open the Hyper-V->VMMS event viewer in Hyper-B.upholland.lancsngfl.ac.uk and check if there are any SPN registration errors or Kerberos related errors? Run eventvwr.msc->Custom Views->Server Roles->Hyper-V

You could also run the following command "setspn /l <domain\machinename>" in the machine "Hyper-B". Substitute the machinename with Hyper-B and the domain name as appropriate. Do you see any entry which has something like "Hyper-V Replica Service\FQDN"?

Praveen

Do you have any 3rd party monitoring tools which is running on Server A or B?

Praveen

I do not have any 3rd party monitoring tools.

I am going to have to put this on hold for a couple of weeks but will post again when I am able to return to the problem.

Thanks for your help so far.

Rob