Re: Migration from bird 1.6 to 2.0.

[Chriztoffer Hansen]

Hi Mike,

On Fri, 10 Jul 2020 at 20:21, Mike Neo  wrote:
> is it recommended to migrate from bird 1.6 to 2.0 if I use bird for an easy 
> bgp router with 2-3 peers?
> What's the difference between 1.6 and 2.0?

There is no active incentive to migrate to Bird2 (yet). As Ross
mentioned, RPKI is supported in Bird2. Bird1 use static ROA tables
(reloadable) for the same functionality.

Most of the worlds largest internet exchanges uses Bird 1.6.x for
their route-servers one way or another. DE-CIX, AMS-IX, Netnod, NL-ix
being amongst the top 5 IX's doing so. I.e. performance considerations
should not be your primary driver to change release train, just yet.

One point to keep in mind is the dev team behind bird has not
officially promoted Bird2 as "the stable" release just yet. And some
major [internal] code changes are still scheduled to happen before
Bird2 is set to be promoted as "the stable release" of the Bird
routing daemon in favour of the current stable v1.6.x branch.

-- 
Chriztoffer

Re: Migration from bird 1.6 to 2.0.

[Ross Tajvar]

I migrated so I could use RPKI.

On Fri, Jul 10, 2020, 2:28 PM Mike Neo  wrote:

> Hi,
>
> is it recommended to migrate from bird 1.6 to 2.0 if I use bird for an
> easy bgp router with 2-3 peers?
> What's the difference between 1.6 and 2.0?
>
> Best regards,
> Mike
>

Migration from bird 1.6 to 2.0.

[Mike Neo]

Hi,

is it recommended to migrate from bird 1.6 to 2.0 if I use bird for an easy
bgp router with 2-3 peers?
What's the difference between 1.6 and 2.0?

Best regards,
Mike

Re: BIRD on physical / virtual server.

[Mike Neo]

Great, thanks!

śr., 8 lip 2020 o 09:19 Kees Meijs  napisał(a):

> Hi Mike,
>
> Saso is correct; we bumped into that one too.
>
> However, as long as you're running BIRD in a VM and OVS is outside the VM
> there's no issue.
>
> K.
>
> On 08-07-2020 08:58, Saso Tavcar wrote:
>
> Hi,
>
> There is a known issue with with Open vSwitch (OVS) performance with BGP.
> Even without OVS we hit IRQ (too many) issue on "physical" network in our
> KVM
> environment.
>
>
> Official OVS quote:
>
> >* We'd accept patches to improve OVS's routing table code.  It's not
> *>* designed to scale to 1,800,000 routes.  We'd also take code to suppress
> *>* the routing table code in cases where it isn't actually needed, since
> *>* it's not always needed.  But we can't take a patch to just delete it;
> *>* I'm sure you understand.*
>
> I tried to apply this patch at that time, but was already useless for
> newer versions:
>
> *https://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20161123/5379b333/attachment.bin
> *
>
> Our workaround was to scale VM with 3 vCPU-s, since our average system
> load is 1.5 for BGP.
>
> You can see what is happening:
>
> [root@bgp1 ~]# top
> ...
>   PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+
> COMMAND
>
> *  654 root  10 -10 1284492   1.0g  20276 R  98.0  27.0   2513:01
> ovs-vswitchd
>   *
>16 root  20   0   0  0  0 S   2.0   0.0  24:45.60
> ksoftirqd/1
>
> [root@bgp1 ~]# ip route show
> ...
> 1.0.0.0/24 via 89.212.xx.xx dev t2-v24-ha proto bird
> 1.0.4.0/24 via 89.212.xx.xx dev t2-v24-ha proto bird
> 1.0.4.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> 1.0.5.0/24 via 89.212.xx.xx dev t2-v24-ha proto bird
>
>
> Routes being constantly added and deleted:
>
> [root@bgp1 ~]# ip monitor
> ...
> Deleted 2620:11d:6000::/42 via 2a01:xxx:xxx::1 dev t2-v26-ha proto bird
> metric 1024 pref medium
> 2620:11d:6000::/42 via 2a01:xxx:xxx::1 dev t2-v26-ha proto bird metric
> 1024 pref medium
> Deleted 2620:11d:6000::/42 via 2a01:xxx:xxx::1 dev t2-v26-ha proto bird
> metric 1024 pref medium
> 2620:11d:6000::/42 via 2a01:xxx:xxx::1 dev t2-v26-ha proto bird metric
> 1024 pref medium
> Deleted 2620:11d:6000::/42 via 2a01:xxx:xxx::1 dev t2-v26-ha proto bird
> metric 1024 pref medium
> 2620:11d:6000::/42 via 2a01:xxx:xxx::1 dev t2-v26-ha proto bird metric
> 1024 pref medium
> Deleted 68.69.37.0/24 via 89.212.xx.xx dev t2-v24-ha proto bird
> 68.69.37.0/24 via 89.212.xx.xx dev t2-v24-ha proto bird
> Deleted 103.115.180.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> 103.115.180.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> Deleted 103.115.180.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> 103.115.180.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> Deleted 2.16.70.0/23 via 89.212.xx.xx dev t2-v24-ha proto bird
> Deleted 88.221.28.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> Deleted 23.50.188.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> Deleted 92.122.68.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> Deleted 88.221.100.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> Deleted 92.123.208.0/22 via 89.212.xx.xx dev t2-v24-ha proto bird
> .
>
>
>
> Regards,
> saso
>
> On 8 Jul 2020, at 08:05, Mike Neo  wrote:
>
> Hi,
>
> what is your experience with installing bird on virtual server (ESXi)? Is
> there any limitation of this kind of deployment for example problems with
> performance etc.?
>
> Regards,
> Mike
>
>
>
>

Check filtered RPKI routes

[Fabiano D'Agostino]

Hi all,
is there a way to check quickly filtered RPKI routes?
I can check the syslog, but if I delete the log I think the only way to
check filtered routes (having import keep filtered enabled) is:

show route table table_name all filtered

but having a lot of tables it is not easy to handle this command for every
single table.

Thanks,

Fabiano