> Doing a "ovs-appctl bond/set-active-slave bond0 eth1", the failover goes > smoothly on the host and the standby interface becomes the active one (which > is on a different switch). > For the kvm guests however, it seems like the uplink switches have to learn > the new situation first and the guests are unreachable meanwhile.
Try doing ifconfig eth1 down instead. This will take carrier down on the NIC causing the upstream switch to flush it's learning table. This is more realistic too, bond's don't typically failover when there isn't a problem, so connectivity loss is expected when using set-active-slave as you're doing. > Because the guest doesn't know about the underlying network change, it > doesn't send a gratuitous ARP like it does with live migrations. Is this a > misconfiguration in openvswitch, since openvswitch is the only one who knows > about the failover? Is there a way to have it send gratuitous ARP requests > for the virtual mac addresses? Something like this could be added to OVS as we currently do it for SLB bonds. But the situation your testing is unrealistic (due to the carrier not dropping) so I'd prefer to avoid it until there's a real-world use case. Ethan > > -- > Frido Roose > > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
