none
How to set MigrationServiceListenerIPAddressList in Hyper-V host WMI

    Question

  • hi I hope to resolve this strange issue in Hyper-V Live Migration IP setting:

    My Hyper-V Live Migration is failing as there is a host local IP "192.168.5.1" that seems to be in the WMI as the 1st IP to use to migrate VM to another host.

    Whenever I try to Live Migration it uses that local IP and fails.

    How to I set MigrationServiceListenerIPAddressList in the WMI for each Hyper-V hosts, to remove that unwanted IP ?

    ------------------------------------- From Hyper-V Powershell  -------------------------------------------------------
    PS C:\Windows\system32> Get-VMMigrationNetwork
    ComputerName : NTNX-1D-HYPERV
    Subnet       : 192.168.20.0/24
    Priority     : 3
    IsDeleted    : False
    Key          :

    ComputerName : NTNX-1D-HYPERV
    Subnet       : 172.27.61.0/25
    Priority     : 5000
    IsDeleted    : False
    Key          :

    ComputerName : NTNX-1D-HYPERV
    Subnet       : 192.168.20.10/32
    Priority     : 1
    IsDeleted    : False
    Key          :

    ComputerName : NTNX-1D-HYPERV
    Subnet       : 172.27.61.20/32
    Priority     : 2
    IsDeleted    : False
    Key          :
    ------------------------------------- WMI data -------------------------------------------------------

    PS C:\Windows\system32> gwmi -n root\virtualization\v2 Msvm_VirtualSystemMigrationService | select MigrationServiceListe
    nerIPAddressList

    MigrationServiceListenerIPAddressList
    -------------------------------------
    {192.168.5.1, 192.168.20.10, 172.27.61.20}

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

    thanks for helping!

    Friday, March 31, 2017 11:59 AM

All replies

  • Cluster or standalone?

    Change the networks used for cluster Live Migrations in Failover Cluster Manager. Right-click the "Networks" node and click "Live Migration Settings".

    For stand-alone, it's on the host settings:


    Eric Siron
    Altaro Hyper-V Blog
    I am an independent contributor, not an Altaro employee. I accept all responsibility for the content of my posts. You accept all responsibility for any actions that you take based on the content of my posts.

    Friday, March 31, 2017 12:58 PM
  • Eric shows how to configure this with the GUI.  Here is a blog post on how to configure a network for live migration by using PowerShell - https://blogs.msdn.microsoft.com/virtual_pc_guy/2013/05/02/using-powershell-to-configure-live-migration-networks-in-a-hyper-v-cluster/

    tim

    Friday, March 31, 2017 1:53 PM
  • hi Eric, Tim,

    Yes the 3 hosts are in a hyper-V Failover cluster. In the FC manager I already unchecked the local host "192.268.5.0/24" private network (which can't seem to be removed, only unchecked).

    I can migrate VMs in FC,  but using Hyper-V manager migration between the 3 hosts fails as they always select the "192.268.5.1" IP for migration. So I want to Modify the order of the MigrationServiceListenerIPAddressList ,  so that "192.268.5.1" is the last, or removome it completely.

     I tried with WMI powershell cmdlet, but it has errors:

    Set-WmiInstance -namespace root\virtualization\v2 -Class Msvm_VirtualSystemMigrationS
    ervice -ComputerName "NTNX-1D-HYPERV" -Argument @{Displayname="MigrationServiceListenerIPAddressList"; Value="192.168.20.10, 172.27.61.20,192.268.5.1"}

    Anyone knows how to remove the private IP "192.268.5.1" from the Migration Address List?

    thanks

    Sunday, April 2, 2017 10:55 AM
  • From the GUI console, show us what the settings are for that address.

    tim

    Sunday, April 2, 2017 11:40 AM
  • The root\virtualization\v2 WMI tree is for Hyper-V only. You cannot control cluster Live Migrations or anything else cluster-related using anything in that branch. The settings that you listed correspond to the second screenshot that I showed. They only impact non-cluster Live Migrations.

    I've been through the clustering WMI tree a number of times and never found anything that corresponds to Live Migration network settings. As far as I know, the only place that you can modify them is in the registry. The root registry key is: HKEY_LOCAL_MACHINE\Cluster\ResourceTypes\Virtual Machine\Parameters. The settings that you manipulate are "MigrationExcludeNetworks" and "MigrationNetworkOrder". But, manipulating these keys by hand is not superior to the PowerShell or GUI methods.


    Eric Siron
    Altaro Hyper-V Blog
    I am an independent contributor, not an Altaro employee. I accept all responsibility for the content of my posts. You accept all responsibility for any actions that you take based on the content of my posts.

    Sunday, April 2, 2017 1:07 PM
  • Thanks Eric, in Registry the "MigrationExcludeNetworks" and "MigrationNetworkOrder" settings are the same as in GUI, so nothing I can do there.

    BUT I saw in the [HKEY_LOCAL_MACHINE\Cluster\Networks] there is the registry key for the Local Network I wanted to exclude or remove or disable or Lower Priority.

    ----------------- Failover Cluster Hyper-V node [HKEY_LOCAL_MACHINE\Cluster\Networks] ----------------

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\Cluster\Networks\e98cefa3-cce1-4107-8645-1270d62f51fb]
    @="≸"
    "Id"="e98cefa3-cce1-4107-8645-1270d62f51fb"
    "Name"="Local Network"
    "Signature"="NETW"
    "Description"=""
    "Role"=dword:00000000
    "Priority"=dword:ffffffff
    "Transport"="TCP/IP"
    "Ignore"=dword:00000000
    "Address"="192.168.5.0"
    "AddressMask"="255.255.255.0"
    "IPv6Address"=""
    "State"=dword:00000003
    "Metric"=dword:000137e1
    "AutoMetric"=dword:00000001
    "LinkSpeed"=hex(b):00,e4,0b,54,02,00,00,00
    "RdmaCapable"=dword:00000000
    "RssCapable"=dword:00000000

    [HKEY_LOCAL_MACHINE\Cluster\Networks\e98cefa3-cce1-4107-8645-1270d62f51fb\PrefixList]
    @="set"

    [HKEY_LOCAL_MACHINE\Cluster\Networks\e98cefa3-cce1-4107-8645-1270d62f51fb\PrefixList\0000]
    @="struct cxl::IPPrefix"
    "address"="192.168.5.0 0"
    "prefixLength"=dword:00000018
    -----------------------------------------------------------------------------------------------------------------------

    Can you advice which setting I should modify to exclude / remove / disable / Lower Priority? It seems there are 3 settings that can achieve that, can you explain them? Their values are the same as the other 2 networks that I enabled for Live Migration in FC manager.

    "Priority" -- Priority value to use 1st/last for Migration ?

    "Ignore"-- Don't use it at all for Migration ?

    "State" -- Can set to 0 to Disable network for migration ?

    How about deleting the Registry key totally on all the FC nodes?

    thanks, chooks

    Monday, April 3, 2017 5:02 AM
  • Hi Sir,

    PS C:\Windows\system32> Get-VMMigrationNetwork
    ComputerName : NTNX-1D-HYPERV
    Subnet       : 192.168.20.0/24
    Priority     : 3
    IsDeleted    : False
    Key          :

    In the original post , that command listed subnet "192.168.20.0/24" ,I didn't get the output in my lab (I mean the IP address 192.168.20.0 shouldn't be used ).

    In addition :

    That IP address (192.168.5.1) can not be found in "networks" in cluster admin console ?

     

    Best Regards,

    Elton 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, April 3, 2017 8:33 AM
    Moderator
  • hi Elton,

    To be clear, I just want to ensure during Hyper-V manager VM migration, not to use the private local network "192.168.5.0" as is is internal hence migration always fails. As you can see, the 3 hosts in FC has the same "192.168.5.1" IP which is local to each host only.

    There is Registry Cluster Network settings which I want to use to Disable/Lower Priority etc the "192.168.5.0" network so it is not used by Hyper-V migration servce. Some VMs are not added in FC, so I use Hyper-V manager for VM migration.

    Monday, April 3, 2017 11:41 AM
  • Thanks Eric, in Registry the "MigrationExcludeNetworks" and "MigrationNetworkOrder" settings are the same as in GUI, so nothing I can do there.

    BUT I saw in the [HKEY_LOCAL_MACHINE\Cluster\Networks] there is the registry key for the Local Network I wanted to exclude or remove or disable or Lower Priority.

    ----------------- Failover Cluster Hyper-V node [HKEY_LOCAL_MACHINE\Cluster\Networks] ----------------

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\Cluster\Networks\e98cefa3-cce1-4107-8645-1270d62f51fb]
    @="≸"
    "Id"="e98cefa3-cce1-4107-8645-1270d62f51fb"
    "Name"="Local Network"
    "Signature"="NETW"
    "Description"=""
    "Role"=dword:00000000
    "Priority"=dword:ffffffff
    "Transport"="TCP/IP"
    "Ignore"=dword:00000000
    "Address"="192.168.5.0"
    "AddressMask"="255.255.255.0"
    "IPv6Address"=""
    "State"=dword:00000003
    "Metric"=dword:000137e1
    "AutoMetric"=dword:00000001
    "LinkSpeed"=hex(b):00,e4,0b,54,02,00,00,00
    "RdmaCapable"=dword:00000000
    "RssCapable"=dword:00000000

    [HKEY_LOCAL_MACHINE\Cluster\Networks\e98cefa3-cce1-4107-8645-1270d62f51fb\PrefixList]
    @="set"

    [HKEY_LOCAL_MACHINE\Cluster\Networks\e98cefa3-cce1-4107-8645-1270d62f51fb\PrefixList\0000]
    @="struct cxl::IPPrefix"
    "address"="192.168.5.0 0"
    "prefixLength"=dword:00000018
    -----------------------------------------------------------------------------------------------------------------------

    Can you advice which setting I should modify to exclude / remove / disable / Lower Priority? It seems there are 3 settings that can achieve that, can you explain them? Their values are the same as the other 2 networks that I enabled for Live Migration in FC manager.

    "Priority" -- Priority value to use 1st/last for Migration ?

    "Ignore"-- Don't use it at all for Migration ?

    "State" -- Can set to 0 to Disable network for migration ?

    How about deleting the Registry key totally on all the FC nodes?

    thanks, chooks


    Anyone can help on what value for the settings to exclude the private local network "192.168.5.0" ?
    Thursday, April 6, 2017 10:34 AM