On Thu, 19 Sep 2019 at 14:22, <[email protected]> wrote: > Just a few examples when you change export policy it resets the peer or the > cockup with RR clearing all sessions or the fact BGP is part of very complex > RDP monolith -to me that's not really "carrier grade" implementation
This happens when export policy breaks update-group. It may sometimes be difficult for operator to understand if it will do that or not, so it's fair concern. Perhaps system should not clear, but tell manual clear is needed for policy change to take effect. If monolith is good or bad, I'm not sure. If you thread you have high performance with some risk. If you have process separation you have IPC problem, and you have low performance and many will solve this by duplicating state. Junos is moving towards multi process model with Junos Evolved, if this will be positive or negative direction remains to be seen. Operationally speaking, BGP in JunOS for us works great, on IOS-XR right now we have sessions where policy isn't what is configured and there is no way to verify which one, and we've propagated leaks because acting configuration isn't the one we've configured. We've not had similar problems in JunOS. This is anecdote, not data. -- ++ytti _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
