Route Servers and Secondary Routes (bird 1.3.10 and debian kernel 3.2-amd64)
Hi Everyone, I have used both examples from Ondrej "Simple Route Server" and "Router server with community based filtering and single RIB", from the gitlabs.labs.nic.cz, to configure 2 Route Servers that need to tranfer to each other via iBGP all the routes they have learned. I thought that the most important parameters, when coupling both Router Servers, where the "table master sorted" and the "secondary" parameter for the iBGP configuration, but my routing table is just showing the Best Route and not all of them. I am pushing to one of the servers via iBGP and "bgpdump/bgpsimple" around 775775 prefixes (www.ripe.net/cata-tools/stats/ris/ris-raw-data). I do not know why but the route server is receiving the 775775 prefixes, filtering them and just showing the preferred ones. I have tried with "show route all filtered", but the command does not show anything. R65500x1 BGP master up 14:11 Established Description: 192.168.0.1 Preference: 100 Input filter: ACCEPT Output filter: ACCEPT Routes: 47423 imported, 0 exported, 47423 preferred <<<---- Route change stats: received rejected filtered ignored accepted Import updates: 775775 0 0 17521 758254 <<<---- Import withdraws: 6 0 --- 2 4 Export updates: 758255 758254 2 --- 0 Export withdraws: 4 --- --- --- 0 BGP state: Established Neighbor address: 192.168.0.1 Neighbor AS: 65500 Neighbor ID: 192.168.0.1 Neighbor caps: Session: internal Source address: 192.168.0.2 Hold timer: 1905/2400 Keepalive timer: 339/800 // CONFIGURATION log "/var/log/bird.log" all; log syslog all; router id 192.168.0.2; define myas = 65500; #### # Protocol template template bgp PEERS { local as myas; source address 192.168.0.2; secondary; import all; export all; route limit 10000; } table master sorted; #### # Configuration of BGP peer follows ### AS65500 - Member1 protocol bgp R65500x1 from PEERS { description "192.168.0.1"; gateway direct; neighbor 192.168.0.1 as 65500; } // LOGS Nov 25 17:06:12 bird: R65500x1 > added [best] 1.0.4.0/24 via 192.168.0.1 on eth2 Nov 25 17:06:12 bird: kernel1 < added 1.0.4.0/24 via 192.168.0.1 on eth2 Nov 25 17:06:12 bird: R65500x1 < rejected by protocol 1.0.4.0/24 via 192.168.0.1 on eth2 Nov 25 17:06:12 bird: R65500x1 > added [best] 1.0.4.0/24 via 192.168.0.1 on eth2 Nov 25 17:06:12 bird: kernel1 < replaced 1.0.4.0/24 via 192.168.0.1 on eth2 Nov 25 17:06:12 bird: R65500x1 < rejected by protocol 1.0.4.0/24 via 192.168.0.1 on eth2 Nov 25 17:06:12 bird: R65500x1 > added [best] 1.0.4.0/24 via 192.168.0.1 on eth2 Nov 25 17:06:12 bird: kernel1 < replaced 1.0.4.0/24 via 192.168.0.1 on eth2 Nov 25 17:06:12 bird: R65500x1 < rejected by protocol 1.0.4.0/24 via 192.168.0.1 on eth2 Nov 25 17:06:12 bird: R65500x1 > added [best] 1.0.4.0/24 via 192.168.0.1 on eth2 Any idea? Thanks in advance, Daniel Gomez
On Mon, Nov 25, 2013 at 06:07:42PM +0100, Daniel Gomez wrote:
Hi Everyone,
I have used both examples from Ondrej "Simple Route Server" and "Router server with community based filtering and single RIB", from the gitlabs.labs.nic.cz, to configure 2 Route Servers that need to tranfer to each other via iBGP all the routes they have learned.
I thought that the most important parameters, when coupling both Router Servers, where the "table master sorted" and the "secondary" parameter for the iBGP configuration, but my routing table is just showing the Best Route and not all of them.
Hello You misunderstood what does 'secondary' option (with 'table master sorted'). This is relevant to outgoing routes only and allows to export the best route that passed the filter (but only one for each net). It does not alter the behavior for incoming routes, which is to keep just one received route for each net (i.e. replace one with the newer). Therefore, you cannot 'couple' both route servers using IBGP. OTOH, perhaps you don't need that - route servers are usually operated two independent, where each client is connected to both. The 'coupling' could be done by add-path extension (which allows to send or receive several routes for the same network over one connection), which is not yet merged to the BIRD. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hallo, Then ,I think the right question is: How can I insert a second best route into the routing table? Daniel Gomez Von: Ondrej Zajicek <santiago@crfreenet.org> An: Daniel Gomez <Daniel.Gomez@synaix.de> Kopie: bird <bird-users@network.cz> Datum: 25.11.2013 18:37 Betreff: Re: Route Servers and Secondary Routes (bird 1.3.10 and debian kernel 3.2-amd64) Gesendet von: owner-bird-users@atrey.karlin.mff.cuni.cz On Mon, Nov 25, 2013 at 06:07:42PM +0100, Daniel Gomez wrote:
Hi Everyone,
I have used both examples from Ondrej "Simple Route Server" and "Router server with community based filtering and single RIB", from the gitlabs.labs.nic.cz, to configure 2 Route Servers that need to tranfer to each other via iBGP all the routes they have learned.
I thought that the most important parameters, when coupling both Router Servers, where the "table master sorted" and the "secondary" parameter for the iBGP configuration, but my routing table is just showing the Best Route and not all of them.
Hello You misunderstood what does 'secondary' option (with 'table master sorted'). This is relevant to outgoing routes only and allows to export the best route that passed the filter (but only one for each net). It does not alter the behavior for incoming routes, which is to keep just one received route for each net (i.e. replace one with the newer). Therefore, you cannot 'couple' both route servers using IBGP. OTOH, perhaps you don't need that - route servers are usually operated two independent, where each client is connected to both. The 'coupling' could be done by add-path extension (which allows to send or receive several routes for the same network over one connection), which is not yet merged to the BIRD. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so." [Anhang "signature.asc" gelöscht von Daniel Gomez/ac/synaix]
participants (2)
-
Daniel Gomez -
Ondrej Zajicek