Issue: When DVMs of HyperV is part of multiple network then multiple IP address are configured ; due to which the DVM doesn't know which network to use to communicate with controller and sometimes it might go into not responding state.
Resolution: Configure " Pool IP range Affinity" feature on HyWorks controller.
Supported versions of controller: 2.5 , GA , SP2 and above
When DVM is part of multiple network then controller/client to DVM communication is generally part of one network. So Pool IP Range Affinity helps controller/client to DVM use specific range
Follow below steps to configure the feature in Registry:
- Create Sub-Key : HKLM\SOFTWARE\Accops\Controller\EDC\SERVICE\Pools\
- Create Sub-Key with Pool Name
- Then Create Multi-Value String Entry
- Its name should start with “Range” (so you can have multiple Range)
As seen in above image, "TestPool" is pool name in Hyworks Controller.
2.In the Value Field enter starting IP address
3.At next line enter end IP Address
4. Add D-Word “IPRangeFilterEnabled”
- Set 1 to enable this feature for the Pool
- Set 0 to disable this feature for the Pool
As seen in above image, the pool affinity has been enabled for "TestPool" and range of IP's is between 172.18.1.5 to 172.18.1.16
●Repeat above steps to have multiple range values
As seen in above screenshot: multiple IP range's are for 10.1.0.5 to 10.1.1.10, 172.16.8.10 to 172.16.8.50 & 172.18.1.5 to 172.18.1.16 are the ranges for pool "TestPool"
Note that in above scenario, with 3 IP ranges , if any VM has IP's from two or more IP range this solution wont work.
4. Restart the service of HyWorks Controller.
1.This feature is only working for HyperV Provider
2.Currently “,” and “;” delimiters supported to report Multiple IP by HyperV
3.If controller is in HA, you need to make the registry entries on both controller and then restart the HyWorks Controller service of primary controller with secondary in maintenance mode.