Forcing replication to a specific NIC

Question

Is it possible to force Hyper-V to use a spesific network interface for replication traffic? I have a dedicated "live migration" interface connecting all hosts together, but HV keeps using  "management interface", that has far
less bandwidth, for replication. Kind of irritating.
Gleb.

Answer 1

Hello Gleb,
Yes, of course you can force Hyper-V Replica to use dedicated network interface.
Here are the steps:
You must edit the hosts file under C:\Windows\System32\drivers\etc\
as the following:
On each Hyper-V host that they are part of the replica, add the IP address for the specific Network Interface that you want to use and fqdn for the second host and vice versa. 1st Host E.g: 172.16.27.12          
HV02.DOMAIN.COM
2nd Host: 172.16.27.11  HV01.DOMAIN.COM
For testing, when you ping the 2nd Hyper-V host from the 1st host using it's fully qualified domain name, you must get reply from the IP address that you specified on the dedicated NIC.
If you would like to Throttle the Hyper-V Replica Network Traffic, you can use the
New-NetQosPolicy cmdlet on TechNet
For example: New-NetQosPolicy “Replication
Traffic from vmms.exe" -AppPathNameMatchCondition *vmms.exe
–ThrottleRateActionBitsPerSecond 100000
And remember to set this settings on both hosts.
Hope this help.
Regards,
Charbel Nemnom
MCSA, MCSE, MCS, MCITP
Blog: www.charbelnemnom.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark
as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.