Steps to reproduce:
- Add an IP address to the cluster (2 nodes running Windows Server 2012) using the Network Load Balancing Manager
- Using PowerShell set the SkipAsSource flag on the IP Address to true (Set-NetIpAddress -IpAddress 192.168.1.10 -SkipAsSource $true). The flag is correctly set.
- Try to reverse the setting (Set-NetIpAddress -IpAddress 192.168.1.10 -SkipAsSource $false). Flag stays as true.
It appears as though Network Load Balancing Services is remembering the setting from someone.
Things I've tried all without success (in no particular order):
- Removing the IP address from the cluster and adding it back in
- Using PowerShell to remove the IP address and add it back in manually (on each host).Flag stays set as true on the 1st node but takes a second before it reverts back to true on the 2nd node.
- Using netsh to remove the IP address and add it back in manually (on each host). Flag stays set as true on the 1st node but takes a second before it reverts back to true on the 2nd node.
- Deleting each host from the cluster (one at a time), removing the registry keys CurrentControlSet\Services\WLBS and
- Removing both hosts from the cluster
- Restarting the hosts
- Using processmon (sysinternals) to try and find a registry entry that might be set when SkipAsSource is set
Does anyone know:
- How to resolve this issue? I'm guessing resetting the TCP/IP stack would work but that's a last resort as it requires an on sight visit to the datacentre.
- Where the SkipAsSource flag it stored?
- How to reset the master/global cluster config?
Thank in advance,
Antony