Route Cause:
When we access 100.100.100.100 at first time, there will be arp info in the External Router. And after we delete vip and create vip 100.100.100.100 again, the MAC change. But there still be ARP cache in external Router.
Solution:
When we create the port, we need send gratuitous ARP to flash the ARP cache in External Router.
Our deploy is on CentOS6.3, there is the following Bug make arping can't work in netns, so I think we can just use ping gateway to reflash the ARP cache on External Router: https://bugzilla.redhat.com/show_bug.cgi?id=963927
Route Cause:
When we access 100.100.100.100 at first time, there will be arp info in the External Router. And after we delete vip and create vip 100.100.100.100 again, the MAC change. But there still be ARP cache in external Router.
Solution: /bugzilla. redhat. com/show_ bug.cgi? id=963927
When we create the port, we need send gratuitous ARP to flash the ARP cache in External Router.
Our deploy is on CentOS6.3, there is the following Bug make arping can't work in netns, so I think we can just use ping gateway to reflash the ARP cache on External Router:
https:/