Den 29. apr. 2016 15.31 skrev "Nick Hilliard" <nick@foobar.org>:
Laszlo Hanyecz wrote:
I'm curious about specific failure modes that can result from this, if anyone can share examples/experience with it.
The canonical pathological case is where the deaggregated prefixes are affected by upstream topology changes and suddenly your optimisations which saved you N% of forwarding lookup table capacity are wiped out to zero and you end up with no ability to look up next-hops.
With two uplinks that is highly unlikely to the point of being impossible. There is no topology change upstream that can cause a situation where it is not possible to do a high degree of aggregation of the full default free routing table before loading it in the FIB. Regards Baldur