G
GHargreaves
I am currently troubleshooting an issue with a failover cluster where the VIP address of the role is unreachable for after a failover (until the arp timeout on the network switch causes the cached entry to expire).
The general consensus appears to be that the ArpRetryCount needs to be set to 3 to ensure that Gratuitous ARP is broadcast and the arp cache updated.
When modifying this setting in RegEdit, and performing a reboot the setting doesn't persist and defaults back to 0. There doesn't appear to be any GPO applied to the servers that would do this and I can't find any other resources that indicate why this would happen.
Each node is using the built in NIC Teaming functionality (Switch Independent, Dynamic Load Balancing, No Standby Adapter)
It is possible to ping the Role VIP address from the same subnet immediately after a failover however not from the wider network (the subnets where the clients connecting to the role reside).
Can anyone shed any light on this or point me in the right direction of where to look next?
Continue reading...
The general consensus appears to be that the ArpRetryCount needs to be set to 3 to ensure that Gratuitous ARP is broadcast and the arp cache updated.
When modifying this setting in RegEdit, and performing a reboot the setting doesn't persist and defaults back to 0. There doesn't appear to be any GPO applied to the servers that would do this and I can't find any other resources that indicate why this would happen.
Each node is using the built in NIC Teaming functionality (Switch Independent, Dynamic Load Balancing, No Standby Adapter)
It is possible to ping the Role VIP address from the same subnet immediately after a failover however not from the wider network (the subnets where the clients connecting to the role reside).
Can anyone shed any light on this or point me in the right direction of where to look next?
Continue reading...