Recursive lookup issue on the 7200 :(, simple fix From: bird-users-bounces@network.cz [mailto:bird-users-bounces@network.cz] On Behalf Of J Boyle Sent: 06 February 2015 11:33 To: bird-users@network.cz Subject: RE: BIRD Issues for a Newbie Hey, this is resolved, no idea why but it's now stable. I will update when I get to the bottom of that. Thanks, From: bird-users-bounces@network.cz<mailto:bird-users-bounces@network.cz> [mailto:bird-users-bounces@network.cz] On Behalf Of J Boyle Sent: 06 February 2015 11:10 To: bird-users@network.cz<mailto:bird-users@network.cz> Subject: BIRD Issues for a Newbie Hi, very new to BIRD, we use Quagga but I'm looking at implementing both. I have a Cisco 7200 peering with BIRD, as soon as I enable the peering the 7200 gets the full internet routing table but then hits 100% CPU until I disable the peering. I have peered the 7200 with Quagga and sent the full table and it has no problems at all, sits at around 40% CPU with the same full table. Here is the relevant config which is very basic, I've changed most of the settings without any change in the behaviour :( protocol kernel { # learn; # Learn all alien routes from the kernel # persist; # Don't remove routes on bird shutdown # scan time 20; # Scan kernel routing table every 20 seconds # import all; # Default is import all # export all; # Default is export none # kernel table 5; # Kernel table to synchronize with (default: main) } # This pseudo-protocol watches all interface up/down events. protocol device { scan time 1000; # Scan interfaces every 10 seconds protocol bgp RR_Test { description "RR_Test"; local as yyyy; neighbor x.x.x.x as yyyy; rr client; # export filter bgp_out; rr cluster id 0.0.0.10; export all; multihop; # import filter bgp_in; next hop self; source address x.x.x.x; ________________________________ NOTICE AND DISCLAIMER This e-mail (including any attachments) is intended for the above-named person(s). If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose. We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you ________________________________ NOTICE AND DISCLAIMER This e-mail (including any attachments) is intended for the above-named person(s). If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose. We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you ________________________________ NOTICE AND DISCLAIMER This e-mail (including any attachments) is intended for the above-named person(s). If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose. We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you