- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
This was a particularly odd issue which I had never experienced before so I thought it’s worth blogging about it.
During a normal MS Failover Cluster failover operation, the node calming the cluster roles sends out a GARP request to notify the networking infrastructure of the MAC address change. The Layer 3 switch / router then updates the MAC address in the ARP table and packets are routed to the node which claimed the cluster roles. Recently I found myself troubleshooting a MS Failover cluster deployment which wasn’t behaving quite in this manner.
Some background info:
So when the active node was A and I failed over the cluster roles to node B, the failover process was completing successfully however the 3 cluster IP addresses would stop pinging and wouldn’t start pinging again until an hour or so… if I reverted back to node A instantly, the pinging would start again.
Looking at the ARP table on the Layer 3 switch I realized that the MAC address associated with the cluster IP addresses wasn’t changing to the MAC address of node B – which is what we would expect as a result of the failover operation.
How to To enable “GARP reply” on Palo Alto
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!