Microsoft Failover Cluster node not sending out Gratuitous ARP requests after a failover

Gustavo Bonasso 101 Reputation points
2021-09-14T10:42:43.787+00:00

DLT-DBDR01
b4:7a:f1:34:67:4b
10. 10.1.16

DLT-DB02
08:f1:ea:6f:23:dd
10. 10.1.12

both nodes on Windows Server 2016 last update on june 2021
We have a Windows Failover Cluster involving node DLT-DBDR01 and DLT-DB02
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ArpRetryCount=3

Network Interface model HPE 331li, teamed via ServerManager

situation:

servers on VLAN1001, clients on VLAN1003

we do a role (10.10.1.19) failover from node DLT-DBDR01 to DLT-DB02, and after capturing packets on the CISCO switch, we don't see any GARP request from DLT-DBDR01
131942-failover.png

so the role is unreachable from the VLAN1003

we then do a clear of the ARP table, and the role starts to be reachable.
oddly enough, if we then do a failback, the request appears on the packet capture
131953-failback.png

I thought this was a switch issue, but why the failback doesn't need an ARP table clear?

Thanks in advance,

Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
1,025 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Gustavo BONASSO 21 Reputation points
    2021-11-12T15:20:48.28+00:00

    hi. it's been a while since i posted this question. i'm still facing this issue.. any ideas? help is appreciated.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.