For the question about router type: I'm asking our vlab team to confirm.
By checking the open-stack dashboard, the floating IP(10.0.0.7) is added as one fixed IP for VM-A;
VM-A port with allowed_address_pair (10.0.0.0/24 - fa:16:3e:63:d0:39)
VM-B port with allowed_address_pair (10.0.0.0/24 - fa:16:3e:b6:d7:5c)
When switchover happened, our application in the VM-B, will do open one raw socket, and send out one GARP with the floating IP (10.0.0.7) with MAC of VM-B on the interface, to notice the router ARP update.
Sorry I don't understand the "And the GARP will be send to out side world with MAC of router external gateway (qg-device) mac or floating agent gateway (fg-device)".
Our system works before, until the openstack upgrade with arp_responder enabled.
Hello Yulong & Kaplonski,
For the question about router type: I'm asking our vlab team to confirm.
By checking the open-stack dashboard, the floating IP(10.0.0.7) is added as one fixed IP for VM-A; address_ pair (10.0.0.0/24 - fa:16:3e:63:d0:39) address_ pair (10.0.0.0/24 - fa:16:3e:b6:d7:5c)
VM-A port with allowed_
VM-B port with allowed_
When switchover happened, our application in the VM-B, will do open one raw socket, and send out one GARP with the floating IP (10.0.0.7) with MAC of VM-B on the interface, to notice the router ARP update.
Sorry I don't understand the "And the GARP will be send to out side world with MAC of router external gateway (qg-device) mac or floating agent gateway (fg-device)".
Our system works before, until the openstack upgrade with arp_responder enabled.
Thanks,
Mark