Isn't there a case when you DON'T want the links aggregated? If you have servers in 2 different data centers, both announcing a 1.1.1.1/20, but one also announces 1.1.1.1/22, and the other also announces 1.1.5.1/22, so the one data center tends to serve 1.1.1.1-1.1.4.255, and the other data center tends to serve 1.1.5.1-1.1.8.255, but if either data center goes down, the whole address range will be served by the other data center? I don't have this setup, but was considering it at some point. More of a curiosity question. -----Original Message----- From: "Alexander V. Chernikov" <melifaro@yandex-team.ru> Sent: Monday, January 23, 2012 11:14am To: "Maciej Wierzbicki" <voovoos-bird@killfile.pl> Cc: bird-users@network.cz Subject: Re: Route aggregation in BIRD - how? On 23.01.2012 20:01, Maciej Wierzbicki wrote:
Hello.
Case study: * importing full BGP table from various uplinks * some routes received by BGP are being exported via OSPF to core1, using filters: (source = RTS_BGP && bgp_path ~ [= * ASNXYZ * =])
Question: how to aggregate routes (whenever possible) before exporting them via OSPF to core?
It is not possible currently. I'm working on BGP route aggregation and I plan to get more or less working code at the end of this week.
Example: lets say that I've received a.b.c.d/22 and a.b.c.d/24 from asnXYZ via BGP. Lets say that I want to export routes with asnXYZ in aspath via ospf to core1 switch. Obviously, a.b.c.d/24 is in a.b.c.d/22, so I would like to export only a.b.c.d/22. Is it doable in bird? If yes, any hint/keywords in doc?