What you need to know
How should an SDN load-balancer probe identify the active node of a guest cluster?
Potentially affected
Administrators running guest failover clusters inside SDN virtual networks.
DSE recommendation
Create a single mapping that shows the same floating address and probe port in the cluster and load-balancer configuration.
Source facts
Network Controller permits a VM to communicate using its assigned IP addresses. Microsoft therefore requires additional configuration for clustering that uses a floating address. Its design exposes that address through a Software Load Balancer VIP and a health probe that directs traffic to the node currently holding it. The cluster address and probe port must match the corresponding load-balancer settings. Microsoft documentation.
Applicability
Identify the guest nodes, virtual subnet, floating address, VIP, and intended probe port. Review the prerequisites for the guest cluster and reserve the actual address before adapting the example.
DSE recommendation
Create a single mapping that shows the same floating address and probe port in the cluster and load-balancer configuration. Have the guest-cluster and SDN owners review it together. Specify which application request will prove that the active node is reachable through the published address.
Verification
Connect through the VIP and record the responding guest node. Trigger an approved ownership move and repeat the request, checking probe state and cluster ownership during the same window. Investigate a probe mismatch or traffic reaching the wrong node before accepting the floating-address design.
Official references
Microsoft Learn: Guest clustering in a virtual network. Source reviewed September 8, 2026.
Review the official source
Guest clustering in a virtual network · Verified September 8, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE