This is timely for me. I recently picked up a customer who became duel homed by virtue of their circuit to me. This customer had been propagating 145 routes via their other provider. With aggregation they only needed to propagate 34. After having the situation explained, the customer was open to fixing their config. Providers should, better than anyone else, understand the benefits of minimizing the size of the global routing table. We could substantially reduce its size by just educating/policing our customers. Jim
Hey all!
We are approaching 40K routes, and this seems to make IBGP in networks with rich external connectivity pretty unhappy.
Without pointing fingers, there are some 9K prefixes that could be removed by proper aggregation/reconfiguration.
ICM-Stockholm-2#sh ip bgp summ BGP table version is 526856, main routing table version 526856 39321 network entries (300167/309954 paths) using 13491704 bytes of memory
I suggest that everyon go look at what they can do, as we are all loosers with the currect situation.
--Peter