On Nov 9, 2015, at 8:21 PM, Donald Sharp <sha...@cumulusnetworks.com> wrote: > From: Dinesh G Dutt <dd...@cumulusnetworks.com> > > Currently, modifications to route maps do not affect already processed > routes; they only affect new route updates. This patch addresses this > limitation.
This is highly desirable, from one point of view, both as a significant convenience and because it keeps tripping up newbies who wonder why their changes aren't having any effect. However... the current behavior is consistent with Cisco's since the beginning of time, and is well understood by most. More, it allows multiple changes to be made in batches, without having to worry about inconsistent states during those changes. While the existing behavior is easy enough to deal with (clear ip bgp...), there is no easy way to get the existing behavior once this patch is in. While I appreciate the convenience it provides, I can also see this patch being a significant PITA from time to time. So I would suggest the ability to go either way, based on a CLI command. The simple version would simply switch behavior between the two modes; a more complex version would queue up changes while "holding" them, and then process them all as soon as the hold is released. ISTM that the more complex version would be a really nice feature to have, but since I'm not writing the code, I'm not going to complain either way. /a _______________________________________________ Quagga-dev mailing list Quagga-dev@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-dev
