I am trying to understand how and why this is working the way it is. We have a pair of Windows Server 2016 Standard servers running a Hyper-V cluster for Remote Desktop Services. This system has been running fine for almost a year and a half without any real problems. The servers are identical in hardware and software. They are updated at the same time to the same levels of update. They are both also running Starwinds iSCSI software.
Server 1
IP 1 - 10.0.0.70 (Primary/Native IP)
IP 2 - 10.0.0.200 (Cluster IP, assigned at cluster setup)
IP 3 - 10.0.254.70 (synchronize address for Starwinds)
Server 2
IP 1 - 10.0.0.71 (Primary/Native IP)
IP 2 - 10.0.0.200 (Cluster IP, assigned at cluster setup)
IP 3 - 10.0.254.71 (synchronize address for Starwinds)
Before I updated these servers last weekend the .200 address was only visible either via the Cluster Manager, ipconfig, or the DNS name 'ServerCluster'. It was something I could not find a place to set and know that I set it up during the original cluster setup. This .200 address could not be seen via the Network Management tool. None of the adapters showed the address thus it wasn't manipulatable. Furthermore there were no errors related to both servers having this IP address.
After applying several updates last weekend one thing I noticed is that the .200 address is now shown on one adapter in the Network Manager and within the same other places it could be seen. I can even delete or change the address if I wanted to. What's strange though is that the Cluster Manager is spitting out a ton of 'duplicate IP address' errors. However, each server is communicating with the other at the .200 address but with the partner server's MAC address. So Server1 is communicating cluster data to 10.0.0.200 at Server2's MAC address for .200.
Can anyone shed some light on this? Are there changes or other updates that I need to apply to rectify the addressing problem?